robbyd at p9i.com
Wed Jan 7 21:49:03 EST 2004
I have a rather large project that uses autotools as well, and has been
ported to cygwin. In my experience the autotools compatibility between the
two isn't all too great out of the box. I usually end up having to
regenerate the autoconf script (and don't even check it in on CVS anymore, I
have a perl script that will generate all that, among other things).
I have no doubt that autotools help with cross-platform portability (in the
UNIX world at least), but they are very sensitive little beasts. :)
----- Original Message -----
From: "Ryan C. Gordon" <icculus at clutteredmind.org>
To: <physfs at icculus.org>
Sent: Wednesday, January 07, 2004 9:40 PM
Subject: Re: [physfs] 1.0.0-rc2
> > Unsurprisingly, this is also the case with a cross-compiling
> > mingw32. I don't know enough win32 magic to be able to help,
> > though.
> I found the problem, but it's not safe to fix it at this point.
> Basically, the autotools on my system don't have important cygwin fixes,
> so the generated ./configure script in the tarball has issues with
> shared libraries on cygwin.
> What you _can_ do is this: after unpacking the source on a cygwin box,
> run these commands:
> aclocal -I /usr/local/share/aclocal
> libtoolize -c --automake
> automake --add-missing --copy --include-deps
> Ignore the warnings from these commands, then just ./configure and make
> as usual.
More information about the physfs