Boost logo

Boost-Build :

From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2008-09-01 14:42:33


Jurko Gospodnetić wrote:
>> I was referring to the use of /boost/install-headers which does not
>> in fact exist.
>> The package.install creates something more like
>> /boost/filesystem//install-headers
> Hmmm... but isn't this target actually the wrong one to use here?
> Isn't the intention here to just install the headers belonging to this
> one library and not all libraries every time? Not sure how that
> 'ideal' would be implemented though as a library can depend on many
> headers from other libraries as well.

I think that this would require that each library specify
a) which headers belong to it.
b) what other libraries it depends on.


A library can specify its headers and the dependencies can be
found automatically.

The former is probably safer, since header scanning is imperfect.

>> Another related problem is to make
>> bjam msvc -n --with-iostreams trunk//install
>> work, where trunk is my working copy.
>> After applying this patch, only the default-build
>> is still wrong.
> Nice to know it's getting better. When you do get it working
> completely - just send the patch in.

Before I work on this, I'd like to be clear on exactly what the behavior
ought to be. The current behavior is that the default build
will be set according to --build-type=... with the default being
--build-type=minimal only if the current working directory is
BOOST_ROOT. This is set in Jamroot's project default-build.

I think that the correct behavior is to apply the default build only to

and the targets created by boost_install.

In Christ,
Steven Watanabe

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at