|
Boost-Build : |
Subject: Re: [Boost-build] Nested projects
From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2009-09-15 02:57:57
Brian Ravnsgaard Riis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Is it currently possible to nest a complete, seperately compilable
> project inside a boost.build project. Say I have a library, foo, that
> can be seperately compiled using boost.build. I use a "externals"
> facility to get a given revision of foo into a nested externals or
> vendor folder under a project that uses foo.
>
> <~/dev/bar>
> + jamroot.jam
> + src
> | + jamfile.jam
> | + *.cpp
> | - *.hpp
> - externals
> - foo
> + jamroot.jam
> - src
> + jamfile.jam
> + *.cpp
> - *.hpp
>
> How would you do this with Boost.Build? I tried the naïve approach and
> get bitten by an error along the lines of "warning: rulename
> $($(project).attributes).get expands to empty string".
I'm not really sure what the "naive" approach boils down to, but did you try
e.g.:
-- dev/bar/externals/foo/jamroot.jam --
...
use-project src : src ;
-- dev/bar/jamroot.jam --
...
use-project /foo : externals/foo ;
alias foo-src : /foo//src ;
[caveat: not tested]
HTH / Johan
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