|
Boost : |
From: David Abrahams (dave_at_[hidden])
Date: 2007-05-10 07:38:13
on Wed May 09 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
> Stefan Seefeld wrote:
>> Sohail Somani wrote:
>>
>>>> * Must be able to directly build, test, run commands, etc. without
>>>> having to inject the generation of external build files into
>>>> the process.
>>> Actually I'm surprised that wasn't the first response to that email.
>>> Maybe CMake can directly build, but I haven't seen it.
>>
>> I'm not sure I understand the requirement.
>>
>> Are you saying the build system must not generate any intermediate files ?
>> What do you mean by 'direct build' ? Why would you care at all about intermediate
>> files ?
>
> I explain some aspect of that requirements in another email. But to
> answer you question directly :-) ...
>
> I don't care about intermediate files as such. What I care about is
> requiring to run *another* build/make/test executable/system/package to
> get from the build descriptions to the resulting target files, or test
> execution.
Well we could of course always front-end-ize the process so it looks
seamless. But why do you care so much?
>From the POV of the edit/compile/debug cycle you can buy considerable
speed by not doing some of the things we end up doing
(auto-configuration, for example) every time you want to test a
change.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk