From: Dirk Griffioen (dirk_at_[hidden])
Date: 2008-05-22 01:36:36
Just a quick update on what I found out sofar ...
- if I comment out every line in our own jamfiles, it works (bjam
- if I enable a small project that only builds one exe, it works (bjam
- if I enable a bigger project, it fails - bjam never returns, uses 100%
cpu and after 5 minutes starts to bheave erratically (memory goes up and
down, cpu too - to no output or reason why)
- if I outcoumment all <use> and <library> in the exe (and its
dependencies), bjam returns, tries to build (which fails, 'cos no paths
etc) but *installs* the bits it can work out
So it has something to do with <use> and <library>: most likely I do not
understand how to use these, from the docs I understood
- use for including, not linking (mostly for header only libs)
- library when you only want to link (and not propagate a dependency
My question the becomes - 'what is the preferred way to define
dependencies?' (Answer - that depends :)
But seriously, some guidelines would be nice, there are:
and off course their combinations (and he keywords I missed)
FYI - The real-project layout is something like:
The exe's and lib make have use of <use> and <library>, utils are mostly
selfcontained or use boost, in the form '/boost/filesystem'
I've been working at this from 2 angles: otucommenting in our project
and adding to a small from-scratch prject to see where it breakes ...
As soon this small project breakes, I will mail the setup so you can
have a look.
-- www.code-shop.com +31 6 411 92 024
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