From: brock_peabody (bpyama_at_[hidden])
Date: 2003-10-03 12:08:29
--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
>Eh... that would mean you depend on "/boost/thread" project, not an
>individual library. This will work, but might not be what you want.
I would rather say "This library depends on Boost.Thread" than to
have to specify the path to a library file, which may be different
on different platforms. To me this was one advantage of V2. I also
really like the ability for a library to be able to specify other
> use-project /boost/thread : /boost/libs/thread/build ;
This does not work ("cannot find Jamfile in directory...") with the
version of Boost.Build that I have (3.01.7). It does find Jamfiles
in sub projects though:
use-project /my_lib : my_lib/build ;
> should work. Testing now... I attach a test project which works
for me with
> CVS HEAD of Boost.Build.
I can't download this from the web interface to Jamboost (it
says "Attachment (not stored)"), which I've been using since the
message haven't been making it to my hotmail account. Would you
mind sending it to me or posting it to the files section?
Do you think I need to get all the latest files from CVS and rebuild?
FWIW I'm really impressed with Boost.Build. I've used MSVC my whole
career and am just getting into cross platform development. I can't
imagine trying to maintain dependencies between hundreds of projects
with plain make files! When I finally understand it I think
Boost.Build V2 will be make it even easier to maintain my systems
than visual studio does.
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