Boost logo

Boost-Build :

Subject: Re: [Boost-build] stage.install problems
From: Johnny Stucklen (stuckj_at_[hidden])
Date: 2009-02-06 14:03:06

Minor correction. The following worked...

alias install : install-all-bin install-all-lib ;

install install-all-bin
    : $(binaries)
    : <install-dependencies>off

install install-all-lib
    : $(binaries)
    : <install-dependencies>on

I previously just tried the install-all-bin target with
<install-dependencies>on somehow thinking it would magically know to install
libraries where I want them. :-P


On Fri, Feb 6, 2009 at 1:50 PM, Johnny Stucklen <stuckj_at_[hidden]> wrote:

> I was using milestone 12, but just grabbed the latest nightly. I was about
> to report back that it didn't work and then noticed the changeset you
> mentioned was in the actual bjam application. :-P After re-compiling that,
> it is significantly faster. It still takes about 1min to start building with
> all the binaries in the install target, but at least it returns. It normally
> took about 20sec to start building. Certainly an improvement although 1 min
> is still a while to wait per build. But, I guess it beats missing libraries
> or building single and multi variants of each. :-P
> -Johnny
> On Fri, Feb 6, 2009 at 12:22 PM, Vladimir Prus <ghost_at_[hidden]> wrote:
>> On Friday 06 February 2009 18:23:04 Johnny Stucklen wrote:
>> > Hi,
>> >
>> > I'm having a bit of problem using stage.install to stage binaries and
>> > libraries in a project I'm working on. My basic problem is that I can't
>> > reliably install all libraries dependencies for the binaries in the
>> project
>> > from the default build directory hierarchy (e.g.,
>> > LIBNAME/gcc-default/debug/threading-multi ...). I realize there is an
>> > <install-dependencies> feature on stage.install that handles just this
>> > problem, but I'm running into the same problem I've seen posted
>> previously
>> > on this and other lists...enabling that for the binaries leads to bjam
>> > never returning (I'm assuming it's due to the number of dependencies).
>> Before we get to carried away with debugging details -- did you try the
>> SVN HEAD version of Boost.Build -- it is supposed to have this issue
>> fixed. You can get a nightly build at
>> Alternatively, here's the patch that should fix this:
>> HTH,
>> Volodya
>> _______________________________________________
>> Unsubscribe & other changes:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at