From: David Abrahams (dave_at_[hidden])
Date: 2006-02-07 14:59:47
Vladimir Prus <ghost_at_[hidden]> writes:
> On Monday 06 February 2006 17:46, Phillip Seaver wrote:
>> How hard would it be to automatically create a Jamfile to be installed
>> along with the libraries?
> It will be rather tricky. Imagine you build/install a project twice, with
> different properties. Then, you'd need to load the previous installed
> Jamfile, add new declarations to it, and write it again. And you should take
> care not to write the same declaration twice, if case you build/install twice
> with the same properties.
> It's doable, but not very easy, and the structure of file must be fixed.
Seems easier than that to me. Can't you just load the Jamfile as
usual and inspect the data structure that creates?
>> That could also help with the problem of some libraries having
>> usage requirements (in the case of boost libs and in the more
>> general case of building and installing libraries with bbv2).
> Alternatively, each installed library libfoo.so can be accompanied by
> libfoo.so.usage-requirements, and whatever Jamroot responsible for globbing
> and declaring prebuilt targets can glob for those files as well. Though it
> would require "read a file" builtin in jam, unless we have one.
-- 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