-
2000.04.18 06:19 "Re: SGI tiff 3.5.5 make install error .....", by Jan Prikryl
-
2000.04.18 09:38 "Re: SGI tiff 3.5.5 make install error .....", by M. L. Welles
-
2000.04.18 14:42 "Re: SGI tiff 3.5.5 make install error .....", by Jan Prikryl
-
2000.04.18 18:00 "Re: SGI tiff 3.5.5 make install error .....", by Sam Leffler
-
2000.04.18 18:36 "Re: SGI tiff 3.5.5 make install error .....", by Chris Hanson
- 2000.04.18 18:51 "Re: SGI tiff 3.5.5 make install error .....", by Sam Leffler
- 2000.04.19 16:48 "Re: SGI tiff 3.5.5 make install error .....", by Roy Darrall
- 2000.04.19 06:20 "RE: autoconf based configure", by Kevin D. Quitt
-
2000.04.18 18:36 "Re: SGI tiff 3.5.5 make install error .....", by Chris Hanson
- 2000.04.18 19:29 "Re: SGI tiff 3.5.5 make install error .....", by Frank Warmerdam
-
2000.04.18 18:00 "Re: SGI tiff 3.5.5 make install error .....", by Sam Leffler
-
2000.04.18 14:42 "Re: SGI tiff 3.5.5 make install error .....", by Jan Prikryl
-
2000.04.18 09:38 "Re: SGI tiff 3.5.5 make install error .....", by M. L. Welles
2000.04.19 13:13 "RE: autoconf based configure", by Bob Friesenhahn
I am very much against autoconf. It assumes the entire world is a hosted environment and barfs if the linker doesn't assume there's something special about main(). As a result, I ended up doing ten times as much work to port the package than if it had just been a straightforward make file and C code.
Autoconf would be targeted specifically to Unix/Linux and Cygwin users. There would still be generic Makefiles to support other environments.
Autoconf does include support for cross-configuration, but this may assume that an ANSI C compiliant main() exists (I don't know). For embedded OSs like VxWorks you would want to use a traditional Makefile as the starting point.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen