4 a.m.
APPROVE
Redirected discussion to xemacs-beta, this needs checking IMO.
Specifically, people on Windows, and non-Linux non-*BSD Unix which
might not have giflib available, or not have it where Jerry thinks you
should have it. :-) (Note you should wait a bit before updating as
Jerry hasn't committed yet.)
Removing the internal support seems a bit drastic. Why not leave it
in for say six months, but completely #ifndef USE_INTERNAL_GIF'ed out
(and with a comment saying "if nobody reports a need by 2010/03/01,
please remove this obsolete code"? If somebody wants to get running
with GIF in a hurry but doesn't have an immediately accessible giflib,
they can just add a
#define USE_INTERNAL_GIF 1
to src/config.h by hand. No need to autoconfiscate this
"USE_INTERNAL_GIF" hack.
Jerry James writes:
PATCH 21.5
The GIF patents have expired. There's no reason to avoid using an
external GIF library anymore. I would like to throw out our internal
GIF support, because the source files have no license information in
them. They are part of the GPLv3 blocker list.
As it turns out, the source files we are using were forked from
giflib, which is commonly used to supply GIF support (Emacs uses it,
for example). However, we've missed out on further development of
that library. The library is currently distributed with an MIT
license, so our internal GIF support is probably okay, but I'd rather
let someone else maintain the code.
This patch removes the internal GIF support code and attempts to find
and use giflib for GIF support. Lightly tested, but more feedback is
welcome.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:17 p.m.
On Sun, Aug 30, 2009 at 9:00 PM, Stephen J. Turnbull<stephen(a)xemacs.org> wrote:
APPROVE
Redirected discussion to xemacs-beta, this needs checking IMO.
Absolutely! Please, would a few of you apply the patch and let me
know if you run into any problems?
Specifically, people on Windows, and non-Linux non-*BSD Unix which
might not have giflib available, or not have it where Jerry thinks you
should have it. :-) (Note you should wait a bit before updating as
Jerry hasn't committed yet.)
Yes, I especially could use some feedback from the Windows crowd. I
tried to update the Windows build files in a way that seemed
appropriate, but I use Linux exclusively these days, both at home and
at work. I remember from my days of hacking Cygwin support several
years ago that there is some place where I'm supposed to put a giflib
tar file, but I don't remember where that place is. Could someone jog
my memory, please?
Removing the internal support seems a bit drastic. Why not leave it
in for say six months, but completely #ifndef USE_INTERNAL_GIF'ed out
(and with a comment saying "if nobody reports a need by 2010/03/01,
please remove this obsolete code"? If somebody wants to get running
with GIF in a hurry but doesn't have an immediately accessible giflib,
they can just add a
#define USE_INTERNAL_GIF 1
to src/config.h by hand. No need to autoconfiscate this
"USE_INTERNAL_GIF" hack.
Mostly because I don't want to wait until 2010/03/01 for GPLv3. :-)
It doesn't seem like such a drastic step to me because (1) we mostly
rely on PNG support, not so much on GIF support [1]; (2) Emacs relies
solely on giflib for its GIF support [2]; (3) giflib is available for
a wide range of platforms; and (4) the change is to be made to the
beta version of XEmacs.
If you insist, I'll add the USE_INTERNAL_GIF hack, but I'd rather get
the license-free code [3] out of our repository sooner rather than
later, and deal with any problems that causes as we identify them.
Actually, I do know of a problem. The animated GIF support is
haywire: they look like Krazy Kops. Must be something wrong with the
timer. I'll have a look before I commit anything.
Footnotes:
[1] There are no GIF files in the core distribution. On the other
hand, xslt-process, jde, and liece contain GIF files.
[2] And they support Windows and a number of non-Linux OSes, too.
[3] Speaking of license-free code, is anyone in touch with Bill Perry?
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:18 p.m.
>>>> Jerry James <james(a)xemacs.org> writes:
Jerry> Absolutely! Please, would a few of you apply the patch and let
Jerry> me know if you run into any problems?
Good news. The patch applied cleanly.
Bad news. By default I didn't get any GIF support when I run
configure. I had to use --with-gif to get GIF. (Without the patch it
seems like the internal GIF-support is used.))
Jerry> Yes, I especially could use some feedback from the Windows
Jerry> crowd.
OK. I'll try the patch on windows.
Jerry> I remember from my days of hacking Cygwin support several years
Jerry> ago that there is some place where I'm supposed to put a giflib
Jerry> tar file, but I don't remember where that place is. Could
Jerry> someone jog my memory, please?
I think there is some instruction on xemacs.org on how to build the
native version where the placement of these libraries are
mentioned. Look there.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:29 p.m.
On Mon, Aug 31, 2009 at 4:18 PM, Mats Lidell<matsl(a)xemacs.org> wrote:
Good news. The patch applied cleanly.
Bad news. By default I didn't get any GIF support when I run
configure. I had to use --with-gif to get GIF. (Without the patch it
seems like the internal GIF-support is used.))
Where is giflib installed on your system? (I think libungif will
work, too, but there's no reason to use that any more.)
OK. I'll try the patch on windows.
Thanks, Mats. I don't have easy access to a Windows box with
development tools, although I do have slightly difficult access to a
Windows box without development tools.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:27 a.m.
>>>> Jerry James <james(a)xemacs.org> writes:
Jerry> Where is giflib installed on your system? (I think libungif
Jerry> will work, too, but there's no reason to use that any more.)
It, libgif.*, is in /usr/lib
Jerry> Thanks, Mats. I don't have easy access to a Windows box with
Jerry> development tools, although I do have slightly difficult access
Jerry> to a Windows box without development tools.
My first attempt was to try a cygwin-build so I installed giflib-devel
unfortunately this requires X11, at least the headerfiles. Why does
giflib require X?
I gave up there. I don't want to install X under cygwin. Is there some
way to solve this?
Next thing to try is a native build. I'll do that in a day or two.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:59 p.m.
On Wed, Sep 2, 2009 at 4:27 AM, Mats Lidell<matsl(a)xemacs.org> wrote:
It, libgif.*, is in /usr/lib
Let me make sure I understand. Without --with-gif, configure doesn't
find giflib. Do you have to specify --with-gif=/usr, or is --with-gif
enough?
Does running autoconf change the situation?
My first attempt was to try a cygwin-build so I installed
giflib-devel
unfortunately this requires X11, at least the headerfiles. Why does
giflib require X?
Because whoever configured your giflib chose to pass --enable-x11 to
the configure script. You'll have to talk to your upstream about
that. Giflib has the capability of converting an image in an X window
to a GIF, for example.
I gave up there. I don't want to install X under cygwin. Is there
some
way to solve this?
Can you install just the X headers and libraries? You don't need to
actually run a server.
Next thing to try is a native build. I'll do that in a day or
two.
Giflib does have Windows support, so I hope this will be a less
painful experience for you.
Thanks for the feedback!
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
10:46 p.m.
>>>> Jerry James <james(a)xemacs.org> writes:
Jerry> Let me make sure I understand. Without --with-gif, configure
Jerry> doesn't find giflib. Do you have to specify --with-gif=/usr,
Jerry> or is --with-gif enough?
Right. --with-gif is enough.
Jerry> Does running autoconf change the situation?
No.
(Moving over to windows)
Jerry> Because whoever configured your giflib chose to pass
Jerry> --enable-x11 to the configure script. You'll have to talk to
Jerry> your upstream about that. Giflib has the capability of
Jerry> converting an image in an X window to a GIF, for example.
Upstream? I thought with cygwin there was one, and only one, upstream?
Jerry> Can you install just the X headers and libraries? You don't
Jerry> need to actually run a server.
I know. I fear though that this might drag in other problem like
endless updates of things I don't want but for a good cause I guess I
can do it ;-)
> Next thing to try is a native build. I'll do that in a day or
two.
Jerry> Giflib does have Windows support, so I hope this will be a less
Jerry> painful experience for you.
Well the problem there is to find out where to install it or how to
point to it or both. I did however some experiment with the native
build a few months ago so I might have an environment almost ready for
that.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:12 p.m.
On Thu, Sep 3, 2009 at 3:46 PM, Mats Lidell<matsl(a)xemacs.org> wrote:
Right. --with-gif is enough.
That's ... weird. I'll look into it. Thanks for the info.
Upstream? I thought with cygwin there was one, and only one,
upstream?
That's what I meant, sorry. The cygwin packager chose to include the
optional X support in the cygwin build.
Well the problem there is to find out where to install it or how to
point to it or both. I did however some experiment with the native
build a few months ago so I might have an environment almost ready for
that.
Thanks for your willingness to help. I appreciate it.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:22 p.m.
On Thu, Sep 3, 2009 at 3:46 PM, Mats Lidell<matsl(a)xemacs.org> wrote:
Right. --with-gif is enough.
I can only see one way this can happen. That's if libgif (or
libungif) is available in the standard place (/usr/lib or /usr/lib64,
typically), but the header file, gif_lib.h, is not.
Where is gif_lib.h on your system?
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:34 a.m.
Hi Jerry
You wrote:
Jerry> Where is gif_lib.h on your system?
/usr/include/gif_lib.h. The funny thing is that it seems to be found
by configure as well. It happly says...
checking gif_lib.h usability... yes
checking gif_lib.h presence... yes
checking for gif_lib.h... yes
...just to wrap it up by saying nothing about it in the Images
sektion.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:05 p.m.
On Fri, Sep 4, 2009 at 5:34 PM, Mats Lidell<matsl(a)xemacs.org> wrote:
Hi Jerry
You wrote:
Jerry> Where is gif_lib.h on your system?
/usr/include/gif_lib.h. The funny thing is that it seems to be found
by configure as well. It happly says...
checking gif_lib.h usability... yes
checking gif_lib.h presence... yes
checking for gif_lib.h... yes
...just to wrap it up by saying nothing about it in the Images
sektion.
Yours
--
%% Mats
Will you send me your config.log from that run? Maybe it contains a
clue. Thanks,
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:56 a.m.
>>>> Jerry James <james(a)xemacs.org> writes:
Jerry> Giflib does have Windows support, so I hope this will be a less
Jerry> painful experience for you.
I tried a native build but I didn't follow quite the procedure you
might have wanted me to do I think. When I downloaded giflib I saw
that it wanted to be "configured". I ruled that out since I didn't
wanted to get any cygwin dependencies. (But maybe GnuWin32-tools can
be used instead to get a native build!? See below.)
Going for the native build I instead wanted to find a prebuilt package
so that I didn't have to struggle with building giflib as
well. Luckily there is such a package in the GnuWin32-kit. So I ended
up with giflib in Program\GnuWin32 and the other libs in src from our
packaging.
After some editing of custom.inc it builds and runs. So what is the
conclusion? I guess if giflib is included in the library package we
supply, so that it is unpacked with the rest in src, the is quite
easy.
I haven't checked GnuWin32-kit for the other libs, but if they are
there, what about using that instead for our own packaging?
I did get a dependency to giflib4.dll that irritates a little. That
dll needs to be handled in an install.
Note: The build was performed with the tools from VS 2005.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:07 p.m.
On Tue, Sep 8, 2009 at 4:56 AM, Mats Lidell<matsl(a)xemacs.org> wrote:
I tried a native build but I didn't follow quite the procedure
you
might have wanted me to do I think. When I downloaded giflib I saw
that it wanted to be "configured". I ruled that out since I didn't
wanted to get any cygwin dependencies. (But maybe GnuWin32-tools can
be used instead to get a native build!? See below.)
Going for the native build I instead wanted to find a prebuilt package
so that I didn't have to struggle with building giflib as
well. Luckily there is such a package in the GnuWin32-kit. So I ended
up with giflib in Program\GnuWin32 and the other libs in src from our
packaging.
After some editing of custom.inc it builds and runs. So what is the
conclusion? I guess if giflib is included in the library package we
supply, so that it is unpacked with the rest in src, the is quite
easy.
I haven't checked GnuWin32-kit for the other libs, but if they are
there, what about using that instead for our own packaging?
I did get a dependency to giflib4.dll that irritates a little. That
dll needs to be handled in an install.
Note: The build was performed with the tools from VS 2005.
Yours
--
%% Mats
I'm pretty clueless about Windows development. What do I need to do
to make this work? Use small words. :-)
I don't understand the bit about a giflib4.dll dependency at all. Can
you expand on that a little?
Thanks,
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5684
days inactive
5693
days old
12 comments
3 participants
participants (3)
-
Jerry James -
Stephen J. Turnbull -
The XEmacs Package Smoketest