From: Rene Rivera (grafik.list_at_[hidden])
Date: 2006-05-11 00:39:36
Felipe Magno de Almeida wrote:
> On 5/9/06, ANDREW MARLOW, BLOOMBERG/ LONDON OF <amarlow1_at_[hidden]> wrote:
>> my biggest problem with an external dep generator is that
>> developers find ways to avoid using it, typically claiming that
>> doing the make depend first slows their build down.
> I dont think that would be necessary in boost.build. This dependence
> tool could be used by bjam automatically. Wouldnt be much difference
> from a user point of view, except for faster incremental compiling. It
> would probably be better used for boost developers, who need
> incremental compiling of boost, or who uses boost.build for its
> projects (which, btw, I'm a user of boost.build for my own projects).
I'm very doubtful about likely gains in speed. Over time I've looked at
the profiling info and current dependency calculation is not the biggest
time hog, although it is one of the biggest memory hogs (because of
having to scan the sources).
I understand that a content specific solution would yield smaller change
sets. But the complexity involved I don't think outweighs the minimal
-- -- 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-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk