On 05/15/14 15:14, Larry Evans wrote:
On 05/14/14 14:58, Charousset, Dominik wrote:
Yes, sh is an alias for bash on my test machines. I fixed the configure script in the master branch.
The FindBoost script supports hints about search paths, in particular BOOST_LIBRARYDIR might be useful: http://www.cmake.org/cmake/help/git-master/module/FindBoost.html. Hope that helps.
I tried the attached wrapper around boost.actor/configure; however, despite setting all the relevant environment variables, cmake still fails to find the boost libraries:
~/prog_dev/boost/sandbox $ . boost.actor.configure.sh ("BOOST_ROOT=" "/home/evansl/prog_dev/boost/boost-modular/modular-boost") ("Boost_DIR=" "/home/evansl/prog_dev/boost/boost-modular/modular-boost") ("BOOST_INCLUDEDIR=" "/home/evansl/prog_dev/boost/boost-modular/modular-boost") ("BOOST_LIBRARYDIR=" "/home/evansl/prog_dev/boost/boost-modular/modular-boost") -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found g++ version 4.8
-- Looking for C++ include valgrind/valgrind.h -- Looking for C++ include valgrind/valgrind.h - found -- Build type: CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:1202 (message): Unable to find the requested Boost libraries.
Boost version: 1.56.0
Boost include path: /home/evansl/prog_dev/boost/boost-modular/modular-boost
The following Boost libraries could not be found:
boost_system boost_context boost_coroutine boost_thread
No Boost libraries were found. You may need to set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost.
Do I need to create a link library for each of these boost libraries? I assumed the above error messages meant it could find the include files for the libraries, but I noticed system and context have build/Jamfiles which, after a brief glance, look like they create a link library.