Subject: Re: [boost] trunk vs release
From: Juergen Hunold (juergen.hunold_at_[hidden])
Date: 2009-05-24 07:35:28
On Thursday 21 May 2009, troy d. straszheim wrote:
> Vladimir Prus wrote:
> > troy d. straszheim wrote:
> > Maybe, we can still have single include directory while achieving
> > the above goal if we make build process create symlinks to
> > directories? That works on Linux, and I believe modern windows has
> > some way to create links too. I am worried about other operating
> > systems, though.
> I share your worry. Probably some scm mechanism should take care of
> it. I'm out of ideas for the moment.
Maybe we should do it like Qt. They use a perl script called "sync-qt"
to build the QTDIR/include tree on demand. The "include" tree then
contains simple header files which just #include the "real" headers
without anything else.
Just clone git://gitorious.org/qt/qt.git and take a look at bin/sync-qt
To see it working, just start a (shadow) build using "configure" and take
a look at the generated include tree.
The release packages contain this tree so end users don't need to have
I think that something like that should be possible with Boost.Build and
-- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold_at_[hidden] ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk