From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-16 08:56:48
On Thursday 16 June 2005 17:30, David Abrahams wrote:
> > "install" moves specified targets to a specified location, and does not
> > care about --prefix options, and about anything user specifies on the
> > command line.
> > The "boost-install" rule will allow user to invoke "bjam install" and
> > "bjam stage" with exactly the same arguments that are allowed at
> > top-level, like --prefix, or --layout. With "bjam install" both library
> > and headers will be installed.
> I think other projects will want that capability too. My question is
> Do we want two separate rules? Should install always respond to
> --prefix= ? Or should it take arguments that tell it to respond to
I think we need separate rules, because "install" is for moving several
targets to a directory, while those --prefix is much complex beast.
> If we do want two separate rules, we should give the one that responds
> to --prefix a more general name, like prefix-install (I dislike that
> particular name, though ;->) and make it available everywhere.
I thought about "package.install", to emphasise that we're installing not just
a bunch of files but a complete packages. And it can generate the pkg-config
files that were discusses on Boost ml, and what else is required for specific
operating system. Maybe "bundle" on OSX.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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