Re: [PATCH] Do not include and in same file

[Graham Leggett]

William A. Rowe, Jr. wrote:

My gut says if we cannot solve this trivial problem over the course of three+

months due to a utter lack of competency in autoconf (and lack of time by
the small handful who understand it), perhaps the project should consider
alternatives to autoconf as we start looking down the road at APR 2.0.0?


detection tools?

Does anyone have any positive experiences with other configuration and feature

But regardless, a build tool needs to do at least this:







Regards,
Graham
--

I recently had to get my hands dirty getting a 17 year old combination C and C++ codebase cleaned up and the build system replaced from scratch, and in the process got quite good at doing autoconf + automake + libtool. We kept the config pretty standard, and found that as long as you keep things simple and straightforward autoconf works pretty well. - Track dependancies properly. If changing a header file does not cause corresponding rebuild of code, the build system is broken. - Be as platform independant as possible. Here autoconf scores lots of points by having had wide exposure and a long history. - Be reasonably straightforward to use. Here autoconf is not as clear, but we did find that a lot of clarity comes from creating your configure.ac's in as standard a way as possible.

smime.p7s
Description: S/MIME Cryptographic Signature