From: David Abrahams (dave_at_[hidden])
Date: 2005-06-16 08:30:38
Vladimir Prus <ghost_at_[hidden]> writes:
> On Thursday 16 June 2005 16:54, David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> > On Thursday 16 June 2005 16:04, David Abrahams wrote:
>> >> Vladimir Prus <ghost_at_[hidden]> writes:
>> >> > Rene also noted that it's no way to install a specific boost library
>> >> > by going to it's libs/whatever/build and running "bjam install".
>> >> > What's the best way to address this:
>> >> > [ ] Introduce new top-level rule 'declare-install-targets' that each
>> >> > library Jamfile will call (pretty easy)
>> >> If you call the rule "install," I'm on board.
>> > 'install' is already taken main rule name. Maybe 'boost-install'?
>> Okay, but what's the difference between the semantics of the rule
>> you're proposing and what "install" already does?
> "install" moves specified targets to a specified location, and does not
> care about --prefix options, and about anything user specifies on the command
> 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
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
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.
> Essentially, "bjam install" in lib dir will be equivalent to
> cd $boost_root
> bjam install --with-<the-library>
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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