Thanks! And along those lines, this should help with a custom name: --buildid=ID Adds the specified ID to the name of built libraries. The default is to not add anything. From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Steve Lorimer Sent: Tuesday, January 29, 2013 5:17 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Custom library names On 30 January 2013 09:18, John Lilley mailto:john.lilley@redpoint.net> wrote: -- Our software simultaneously runs 32-bit and 64-bit versions of itself, and things are easier if the library names reflect this (e.g. inject _x64_ and _x86_ into the names). from ./b2 --help --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 - Names of boost binaries include the Boost version number, name and version of the compiler and encoded build properties. Boost headers are installed in a subdirectory of <HDRDIR> whose name contains the Boost version number. tagged -- Names of boost binaries include the encoded build properties such as variant and threading, but do not including compiler name and version, or Boost version. This option is useful if you build several variants of Boost, using the same compiler. system - Binaries names do not include the Boost version number or the name and version number of the compiler. Boost headers are installed directly into <HDRDIR>. This option is intended for system integrators who are building distribution packages. The default value is 'versioned' on Windows, and 'system' on Unix. Not sure about putting your own label in the name