I have to disagree on the convenience of this. If you are using autolink (and maybe boost.build), then it does not matter, but if as a user of boost, you are using another build system, it is usually more convenient to specify once and for all different search paths for different build configuration, and then use as much as possible the same file name for all configs (I know that the name is already very much dependent on the configuration in boost, and I consider it a major hindrance), instead of having to write a different file name for each library in each configuration.

---

Loïc

De : Boost-build [mailto:boost-build-bounces@lists.boost.org] De la part de Ashutosh Warikoo
Envoyé : vendredi 3 avril 2015 10:59
À : boost-build@lists.boost.org
Objet : [Boost-build] Add CPU Architecture To The Library Name

I would like to propose a change where boost libraries would include the CPU architecture x86 or x64 etc to the library name. I have tried doing this in the boostcpp.jam but failed. This will be very convenient as when the build is versioned all the files can reside in the same directory & build process is more convenient.
Please advise.