From: Doug Gregor (dgregor_at_[hidden])
Date: 2007-05-09 15:04:57
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 /
>> ... 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
I don't understand this requirement. Are you saying that something like:
Does not meet the build-system requirements?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk