Subject: Re: [Boost-build] bcp rule
From: Matthew Chambers (matthew.chambers_at_[hidden])
Date: 2009-08-19 19:17:39
The implementation was a painful trial and error process, but I finally
have something that's almost ready for a project to use. I have to hook
up the bcp exe target to the action instead of using the hardcoded path.
I had to modify bcp to add reading the module-list from a file because
it can get very long, and doing it piecemeal means way too much
redundant scanning! So I'll (we'll?) have to use a custom version of
that until it gets patched in.
Here's a basically self-contained test case:
I actually put the code in grafik's boost.jam though since that was
simpler than adding a new module and making it depend on boost.jam.
Perhaps this is something that would make sense in the official
boost-build distribution? That would presumably entail using the main
boost build Jamfiles instead of grafik's external build system.
Matthew Chambers wrote:
> 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
> : # requirements
> ] ;
> 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.
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