On Apr 17, 2013, at 8:50 AM, Klaim - Joël Lamotte
On Wed, Apr 17, 2013 at 12:50 PM, Mathias Gaunard < mathias.gaunard@ens-lyon.org> wrote:
[snipped to the essence]
Of course you cannot put both 32 or 64 bit in there without making subfolders.
This is the problem exactly that I'm pointing. I can obviously set the library dir using BOOST_LIBRARYDIR but I then have to do it each time I need to work on CMake files of the projects and need to delete cache and configure from scratch.
TBB puts its libs in intel64 or ia32 sub directories which isn't all that common of a naming scheme in my experience but is certainly usable.
CMake's FindTBB knows that convention which helps it find the right binaries depending on the configuration/architecture choosen which is what I point is lacking with Boost, because of the lack of convention.
I'm not saying boost should use one convention in particular, just that it should provide a convention so that I or someone can patch the FindBoost module.
I see no reason against choosing a subdirectory structure in which to place 32 and 64 bit libraries. However, if Program Files is the install location, Windows already distinguishes between them: Program Files and Program Files (x86). IOW, if that's the install location, the subdirectories aren't needed (though one can still be used in each location). I vote for simple, straightforward names, like 32 and 64, for the subdirectories, BTW. Having said that much, naming the directories with much of the platform and architecture information, while simplifying the library names, would be nicer IME. ___ Rob (Sent from my portable computation engine)