Boost logo

Boost-Build :

Subject: Re: [Boost-build] bcp rule
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-08-22 04:24:06

On Wednesday 19 August 2009 Matthew Chambers wrote:

> Hi,
> In additional to tarball capability, I'd like the ability to build and
> run bcp by calling a rule with a list of targets and/or files to scan
> for boost dependencies and a destination path for the dependencies to be
> copied to. A calling syntax as simple as:
> [ bcp
> : # sources
> some-lib-target
> some-exe-target
> /path/to/some-file.cpp
> : # requirements
> <location>/path/in/which/to/put/dependencies
> ] ;
> would be excellent. This capability would synergize with a tarball rule
> like mine or John Bito's suggestion.
> Since bcp is simple to build but has some boost dependencies
> (filesystem, regex, and prg_exec_monitor), I found it expedient to put a
> prototype bcp rule in the boost.jam extension written by grafik:
> We're already using boost.jam in our project to set up and build our
> project's boost dependencies, and I've added support for a few extra
> libraries as well. I just added support for the test library to get bcp
> to build.
> Has anybody else using boost-build land done something similar? Is
> bcp.jam already out there and I missed it? If not, I figure this will be
> a great addition to grafik's boost.jam, or possibly a corollary to it.

FWIW, speaking of Jamroot you've passed to me on IRC, where you got
"could not construct" issue. I've tracked that down to a bug
in generator logic, which specifically triggered for generators
with multiple source types one of them being EXE. I've checked in the

- Volodya

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