[cmake-developers] [CMake 0015551]: Boost libraries (.dll & .lib) should be found automatically inside the specified BOOST_ROOT directory

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
http://public.kitware.com/Bug/view.php?id=15551 
====================================================================== 
Reported By:                Zack Snyder
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   15551
Category:                   CMake
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2015-05-01 13:58 EDT
Last Modified:              2015-05-01 13:58 EDT
====================================================================== 
Summary:                    Boost libraries (.dll & .lib) should be found
automatically inside the specified BOOST_ROOT directory
Description: 
The boost binaries are not found when they are located under a certain sub
directory in BOOST_ROOT.

I downloaded the prebuild boost binaries from:
http://sourceforge.net/projects/boost/files/boost-binaries/
That will install the boost headers and libraries within one folder.
The folder of the binaries is called e.g. "lib32-msvc-12.0" or "lib64-msvc-12.0"
These folders are located under the BOOST_ROOT directory.

Finding boost within cmake will not work for the binaries, i.e.:
find_package(Boost COMPONENTS chrono system)
this will result in an error.

The user has to specify the environment variable BOOST_LIBRARYDIR.
e.g. set BOOST_LIBRARYDIR=%BOOST_ROOT%/lib64-msvc-12.0
and of course for 32 bit another directory.

Request:
1)
Is it possible that CMake can automatically iterate through the directory of
boost and find this libraries? Or maybe you can add support to look after a
directory called "lib64-*" or "lib32-*" and look into those.
2)
It should be also automatically found the correct binaries architecture for the
currently used compiler, e.g. 32bit binaries for 32 compiler, etc...

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2015-05-01 13:58 Zack Snyder    New Issue                                    
======================================================================