Boost logo

Boost-Build :

From: Greg Wilding (greg_at_[hidden])
Date: 2006-04-17 15:15:42


Hi Vladimir,

I posted the infromation you requested last week, did you get a chance to
look at it yet?

Thanks,
Greg

----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
Newsgroups: gmane.comp.lib.boost.build
Sent: Friday, April 07, 2006 12:40 AM
Subject: Re: bjam slow, can I disable the dependency check?

> On Thursday 06 April 2006 20:55, Greg Wilding wrote:
>
>> I'm wondering of there is a way to disable the dependency check
>> (binding?)
>> when bjam is invoked. I find that 95% of the time I only need to compile
>> one file and then re-link an executable.
>>
>> I know this sounds like heresy, so here's a little background so you know
>> where I'm coming from... My team is using boost to build a project that
>> consists of around 8000 source files organized into 100 or so subprojects
>> (Jamfiles). The build produces about 50 binaries from a large library of
>> shared source code. The build works for Linux and Solaris.
>>
>> We are using boost because we require a reliable incremental build after
>> a
>> workspace has been updated. When bjam is invoked, it takes around 60
>> seconds before any compiling starts on a 3Ghz Machine (I'm assuming that
>> most of this time is checking dependencies).
>
> Hi Greg,
>
> for "bjam foo.o" I think the dependency check itself should not take any
> time,
> and the delay you observe is probably caused by something else. Can you
> run
> bjam with:
>
> bjam -n -d+10 > profile
>
> and send me the output so that I can find where the most time is spent?
> Also,
> are you using Boost.Build V2 or V1?
>
> - Volodya
>
> --
> Vladimir Prus
> http://vladimir_prus.blogspot.com
> Boost.Build V2: http://boost.org/boost-build2
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>


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