From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-05-09 14:53:44
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.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk