Boost logo

Boost-Build :

Subject: Re: [Boost-build] Newbie questions
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-07-13 12:28:59


AMDG

Boris Schaeling wrote:
> On Mon, 13 Jul 2009 14:17:37 +0200, Vladimir Prus <ghost_at_[hidden]>
> wrote:
>> [...]Yes, <os> is old feature. Use <target-os> or <host-os> these days.
>
> As the documentation doesn't mention <host-os> I wonder how to find
> out which features (and rules) exist. Is there any Jamfile which
> defines all features (and rules) and can be used as an always
> up-to-date reference? I sometimes read about features in this mailing
> list and wonder how people knew that they exist.

There's a list of features here, but it isn't complete.
http://www.boost.org/boost-build2/doc/html/bbv2/advanced/builtins/features.html
If you really want to look at the source, most features are defined
in tools/builtin.jam

>> [...]At present, Boost.Build is not checking if it's inside Boost
>> tree, or not.
>
> Then my understanding is correct that it is impossible to link to a
> Boost C++ library without using a hardcoded path in a Jamfile? I ask
> as I've seen sometimes variables used like BOOST_ROOT or BOOST_PATH.
> They are not automatically inherited or set though but must have been
> defined in a project's Jamfile?

You can link to a boost library using
/boost//iostreams (e.g.) if you have
use-project boost : path/to/boost ;
somewhere. It doesn't have to be in Jamroot.
It can be in one of the configuration files.

In Christ,
Steven Watanabe


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