From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-09-07 01:22:32
On Tuesday 05 September 2006 08:11, K. Noel Belcourt wrote:
> Does anyone know if the install or package.install supports
> installing the source, not just the headers? From the documentation
> it's clear that one could separately install the executables,
> libraries and headers, but I can't determine if it's possible to
> install the source that the libraries are built from.
> The reason I want this capability is that we have two end users, one
> that relinks the executables with our libraries and has no need for
> the source. The other does a full system build from the source.
> It's this second use case that I'd like to try to solve, possibly
> using the install or package.install if they can support it.
I think if your second user wants to be able to build everything to source,
you need to build complete source package by:
your_favourite_version_control_system checkout whatever && tar ......
Really, for just packing everything there's no need to use Boost.Build.
It's possible to make Boost.Build install everything, just like it's done for
headers in Boost's Jamfile.v2 -- you point it to a list of headers, specify
<install-source-location> and you're set up. But again, use it only if
wholesale packing of fresh checkout is not going to work.
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