On Thu, 2003-07-31 at 14:27, Frank A. Uepping wrote: > Hi, > assume someone has finished a software project and wants to distribute it > with autoconf. Currently the software compiles and runs on the platform of > the developer; though the developer is interested to get the software run on > other platforms as well, if there is a need (note, the developer has no > access to the other sites). > Autoconf has many feature test macros that allow for testing verything. > Should the developer analyze its software for all the required features > it needs and fit out configure.ac with a test for it (which will makec > onfigure fail if the test fails). > Or should the developer distribute its software with a minimal configure.ac > and let the compilation fail if something is incompatible. > What is the right strategy?
To the other comments I'll add this: view configure's ability to "fail fast" when things aren't going to work as a side effect of its role. Its role is to make different configurations work. If you can't make it do that, adding logic that does nothing other than fail fast is a waste of time. -- Braden McDaniel e-mail: <[EMAIL PROTECTED]> <http://endoframe.com> Jabber: <[EMAIL PROTECTED]>
