Boost logo

Boost-Build :

From: Nicola Musatti (Nicola.Musatti_at_[hidden])
Date: 2006-11-17 09:15:14

Vladimir Prus <ghost <at>> writes:
> On Friday 17 November 2006 16:19, Nicola Musatti wrote:
> > Vladimir Prus <ghost <at>> writes:
> > > tools/build/v2/tools/common.jam has this to say:
> > >
> > > # On borland, version is not added for compatibility
> > > # with V1.
> > > if $(tag) = bcb
> > > {
> > > version = ;
> > > }
> >
> > This would be correct for the generic 'borland' toolset from V1, but not
> > for the release specific ones, such as 'borland-5_6_4'.
> I think you'd need to bring it up with John Maddock. The naming of libraries
> should be coordinated with the auto-linking code, and I can remove those
> three lines any time if you figure out what's the right behaviour.

There are two different aspects of this issue: one is the synchronization
between Boost.Build and auto-linking and the other are the use cases supported
by BBv1. I agree that the first one is essential and the current situation is
coherent; auto-linking doesn't use compiler release numbers for borland and
neither does BBv2.

On the other hand BBv1 supported the use of release numbers in conjunction with
explicit linking (i.e. with auto-linking disabled) for the borland-5_5_1 and
borland-5_6_4 toolsets. This is useful because it makes it convenient to have
libraries for different compiler releases available from the same Boost
installation. It would be nice to have this feature available also in BBv2, e.g.
by recognizing a 'borland-*' style toolset in the code fragment you posted (I'm
not familiar with how BBv2 works, so I don't know if this suggestion makes any

Hopefully at a later time it will also be possible to support versioning for
Borland also in the auto-linking code.

Thank you for your attention!

Nicola Musatti

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