Sam Varshavchik <[EMAIL PROTECTED]> writes: > Lloyd Zusman writes: > >>> And yes, beginning with 0.48, the configure script did get somewhat longer. >>> >>> It's really out of my hands. I don't like myself how bloated autoconf >>> and automake has become. But, that's the devil you know, and there are >>> no better build toolchains out there. >> Well, I think that there is a way have all of the pieces of a >> multi-component package re-use the system-specific configuration >> settings that are determined in the intial "configure" step in the >> topmost directory. > > There is, and this is done already. > > Unfortunately, most of autoconf isn't that smart. Only small pieces > are.
Yeah ... during "configure", each sub-component goes through the same set of determinations about which C/C++ compiler to use, whether all the needed libraries are present, etc. On my system, it takes several minutes to repeat these same tests for each of the Courier sub-components. It doesn't appear like those values get cached at all. I'm not sure, but I seem to remember seeing other autoconf-based systems cache all that stuff for the sub-components. I'll see if I can find an example. -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
