Christopher Woods wrote:
Rene Rivera wrote:
Braden McDaniel wrote:
Is it possible to suppress generation of the unversioned .lib file when building on Windows? ] cd <boost-root> ] bjam --help ...snip... --layout=<layout> Determines whether to choose library names and header locations such that multiple versions of Boost or multiple compilers can be used on the same system.
versioned (default) - Names of boost ...
system - Binaries names do not include ... ...end-snip...
HTH.
The default build on windows builds both versioned *and* unversioned libs (at least for 1.34.0 - can't remember back to 1.33.1 building). If specifying "--layout=versioned" on the bjam command line results in *only* versioned libs then the bjam 'default' is actually something else, no?
The libs versioned creates are internally versioned. It only creates *links/copies* with the unversioned names. For example, in Windows, if you link to the unversioned DLL link library (boost_*.lib), the resulting binary will depend on the versioned DLLs. Same applies on the Unix side. The libs produced by the system layout, are built internally without the version info (if I remember correctly). -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo