On Thu, Dec 31, 2009 at 21:30, Ersek, Laszlo <[email protected]> wrote: > On Thu, 31 Dec 2009, rupert THURNER wrote: > >> we compile quite a lot of packages and most of them produce shared >> libraries, and none of them uses the gnu linker, see >> http://www.opencsw.org/packages. maybe there is a chance to adjust the >> configure so it takes care of the differences, linker and header files? > > Oh, that wouldn't be much work, or fragile at that :) > > http://www.fortran-2000.com/ArnaudRecipes/sharedlib.html > > Please don't suggest autoconf & friends, either :)
i share yours and antonios view that a line of code which does not exist cannot be wrong, and it cannot be executed - so there is a tendency to have less bugs and quicker programs. lacos friendship with autotools like automake, autoconf, libtool, m4, ... made me look a little into build tools. this is what i found: * http://code.google.com/p/synergy-plus/wiki/BuildTool comparison cmake - scons - swtoolkit * http://code.google.com/p/waf/wiki/WafAndOtherBuildSystems comparison waf - cmake - ant - maven - scons - fbuild * http://lwn.net/Articles/188693/ why/how kde switched to cmake * http://scons.org/ * http://code.google.com/p/swtoolkit/ * http://cmake.org/ * http://code.google.com/p/waf * http://buildr.apache.org/ * http://maven.apache.org/ so, if you would ask me now to suggest something it would be something like cmake, waf. but i will also ask what it means to drop in gnu ld into our build system. rupert. _______________________________________________ Lzip-bug mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lzip-bug
