On Fri, Feb 6, 2009 at 1:50 PM, Johnny Stucklen <stuckj@gmail.com> 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@cs.msu.su> 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 http://boost.org/boost-build2

Alternatively, here's the patch that should fix this:

http://svn.boost.org/trac/boost/changeset/44195

HTH,
Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build