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