From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2005-06-17 20:05:18
On 6/17/05, Stefan Seefeld <seefeld_at_[hidden]> wrote:
> Caleb Epstein wrote:
> > On 6/17/05, Stefan Seefeld <seefeld_at_[hidden]> wrote:
> >>Right. I think I wasn't very clear: I believe generating and installing pc files
> >>for all boost libraries as part of the boost.build process is fine. Yet some
> >>systems package the libraries differently (renamed libraries, different installation
> >>prefixes, etc.), so it must be possible to modify those files.
> > If the vendors install things "the right way" (e.g. using bjam, and
> > possibly using the lightly documented --layout flag -- see
> > BOOST_ROOT/Jamfile), then bjam ought to be able to generate the .pc
> > files with the correct settings.
> I didn't know bjam supports packaging a la rpm, deb, etc.
> FWIW, everybody has his own idea about what 'the right way' is, and imposing
> only a single possible way seems to me a bit narrow minded and unrealistic
> in this context. FWIW.
Ok, there is surely more than one "right way", but I was just
suggesting that a vendor can build a system-specific package (rpm,
deb, etc) from the boost sources without needing to bang on the build
system very much. "bjam --layout=system --prefix=tmp/usr install" or
-- Caleb Epstein caleb dot epstein at gmail dot com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk