On May 9, 2007, at 2:53 PM, Rene Rivera wrote:
Doug Gregor wrote:
On May 9, 2007, at 2:20 PM, Stefan Seefeld wrote:
FWIW, that's the typical GNU (autotools) build system procedure: You create a build directory, run $(srcdir)/configure from there, specifying any build options, and then 'make'.
Thus, different build variants would all end up in distinct build directories, outside the source directory they were build from (and are dependent on).
This approach is very natural for people working with autoconf / make.
... and it works better for the CMake model, where one generates build rules for a specific environment (makefiles, VC++ solutions, XCode projects, etc.).
Speaking of that, another requirement:
* Must be able to directly build, test, run commands, etc. without having to inject the generation of external build files into the process.
I don't understand this requirement. Are you saying that something like: configure make Does not meet the build-system requirements? - Doug