On Wed, 18 May 2005, Ed Hartnett wrote:
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
What version of libtool are you using?
I'm using 1.5.10. I will check out the libtool web page and try and get something more recent to work with.
Just a little reality check here: when it works for you, you end up with a windows DLL file ending in .dll, correct?
Yes. For example, "magick/.libs/libGraphicsMagick-2.dll".
Thanks for the help! When I get our library's configure files capable of building windows DLLs, I will build a shrine to libtool and mingW programmers, with life-sized statues, and hire ten computer science students to meditate there on the impermanence of existence, the putrefaction of the flesh, and the difficulty of maintaining (and testing) multiple build environments.
Unfortunately, MinGW and libtool have not always been the best of friends. However, it is well worth the effort if you consider that Windows is just one of many targets. There is no valid reason that one OS should take more than 10X the effort of any other OS to support. MinGW is free, while other compilers may cost lots of $$$. Libtool helps reduce the effort (when it works).
The operation of libtool for MinGW should be very similar to Cygwin. One big difference is that the result starts with 'lib' rather than 'cyg'. Another difference is that Cygwin can be counted on to have a richer toolset available than MinGW so some tests are different for MinGW.
I suggest installing the 'MSYS' shell environment for MinGW. It is very similar to Cygwin, but much smaller. The install takes only a few minutes. That is what I have tested libtool under. Libtool may behave differently if it is executed under Cygwin. Building under Cygwin while targeting MinGW is essentially a cross-compile.
Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
