Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-04-26 05:01:51

On Sunday 09 April 2006 10:15, Jim Douglas wrote:
> Now that the regression tests for the QNX/qcc toolset are running OK I
> thought I would test building the libraries as a user would after
> downloading the source. I tried this natively on QNX and also cross
> compiling on Windows.
> The first observation is that shared libraries (.so) are produced by
> default, whereas bbv1 produced static libraries (.a). Is this meant to
> be a user choice, and if so, how do I change it?

Using link=static on the command line.

> On bbv1 both debug and release versions of the libraries were produced.
> With bbv2 I only get debug.

This is

> I note that the --with/without commands are still recognised. Is this
> the correct current syntax or has it been superceeded?

V2 is the same as V1 in this respect.

> I tried a 'stage' build and on QNX I end up with 3 copies of each
> library with the extensions '.so.1', '.so.1.34' & '.so.1.34.0'. On
> Windows I just get a single copy with a plain '.so' extension - as it
> should be!

Can you clarify if there's anything wrong with that? 3 copies on Linux (which
should be symlinks, in fact), is the standard behaviour.

> QNX does have a system of using a '_g' for debug libraries e.g.
> libboost_filesystem.a & libboost_filesystem_g.a would be the release and
> debug variants. I wondered if I could incorporate a rule to do this for
> the qcc tools?

You should be able to tweak the 'rename' rule in 'stage.jam', but then for
QNX, the library names will be different then on all other platforms.

- Volodya

Vladimir Prus
Boost.Build V2:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at