Subject: CGAL users discussion list
List archive
- From: Chris Marsh <>
- To: <>
- Subject: Re: [cgal-discuss] Boost is not found when compiling my own code
- Date: Tue, 8 Aug 2017 14:22:59 -0600
- Authentication-results: mail3-smtp-sop.national.inria.fr; spf=None ; spf=Pass ; spf=None
- Ironport-phdr: 9a23:RGXSFRNYFXWId3ZxGdgl6mtUPXoX/o7sNwtQ0KIMzox0Lfr/rarrMEGX3/hxlliBBdydsKMUzbKO+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZPebgFLiTanfb9+MAi9oBnMuMURnYZsMLs6xAHTontPdeRWxGdoKkyWkh3h+Mq+/4Nt/jpJtf45+MFOTav1f6IjTbxFFzsmKHw65NfqtRbYUwSC4GYXX3gMnRpJBwjF6wz6Xov0vyDnuOdxxDWWMMvrRr0yRD+s7bpkSAXwhSgFOT438G/ZhM9tgqxFvB2svAZwz5LObYyPKPZyYqHQcNUHTmRBRMZRUClBD5uiYosPFeoBPP1YpJT6qVQUtxu+HgmsD/7oxzBUhn/2x6w60/87HQHDxgMgBckOsHTPodXoL6cdS/u1zKrSwTrfdfxbwDHw45XGfBAmpPGDR7NwcczJxEYzFwPFlFSQqZfgPzyPzOQNqGib4/B8Wu21jWMstgJ/oiC3y8sxlIXEhZgZxk7K+Ch32oo5O8C0RU5hbdK6HpZdtDmWO5VqTs4mWW1luyY3xqcbtZO/YiQG0okryh3DZ/GBboOG+AjsVPyLLjd9nH9leKywhxK18UW4z+3zTMi00FJQoipYidnDrGsN1x/J5sebUPRx5kah2TCR2ADP8uxIPF44mKnBJ5I/zLM9mIAfvVreEiL2gkn6kqGbe0Y89uit8evnY7HmppGGN49zjwHzKrghmsylAeQ5KQgCRW2b9v6m1L34/U30W6hKjuYsnanCs5DWP9gUqbShDw9Pzokj8wq/Dyuh0NkAgXYHI0hKeBaeg4f0OlHOO+z3Deqkg1S3izpr3PDHPrj5AprXNHTDkbHhfax860FG0gYzw8pftNpoDeRVK/36Xgr9tcfTEwQiGw2y2efuTttngNAwQ2WKV4SZKqLJ+XqB/Pkva72HZJUUo3D4IuI+59bzlnYimhkWdP/6jtMsdHmkE6E+cA2ian32j4JZHA==
CMake caches a lot of values, and my guess is you're still seeing these cached values. If you place your CMakeLists.txt file (for your project) in a clean folder, does it work?
Alternatively, I use this in a bash script to clean out all the cmake's files to start fresh
#!/bin/bash
CMAKECACHE=`find . -type f -name "CMakeCache.txt"`
rm -rf $CMAKECACHE
CMAKEFILES=`find . -type d -name "CMakeFiles"`
rm -rf $CMAKEFILES
MAKEFILES=`find . -type f -name "Makefile"`
rm -rf $MAKEFILES
CMAKEINSTALL=`find . -type f -name "cmake_install.cmake"`
rm -rf $CMAKEINSTALL
CMAKETEST=`find . -type f -name "CTestTestfile.cmake"`
rm -rf $CMAKETEST
On 8 August 2017 at 14:10, Michael Bieri <> wrote:
Ok, I tried to do this, but I get the following result when running it with --trace:/my/project/CMakeLists.txt(25): set(Boost_NO_SYSTEM_PATHS TRUE )/my/project/CMakeLists.txt(26): set(BOOST_ROOT /my/boost )/my/project/CMakeLists.txt(27): find_package(Boost REQUIRED )/usr/share/cmake/Modules/FindBoost.cmake(163): if(NOT Boost_NO_BOOST_CMAKE )/usr/share/cmake/Modules/FindBoost.cmake(166): if($ENV{Boost_DIR} STREQUAL )/usr/share/cmake/Modules/FindBoost.cmake(167): if(NOT $ENV{BOOST_ROOT} STREQUAL )/usr/share/cmake/Modules/FindBoost.cmake(168): set(ENV{Boost_DIR} $ENV{BOOST_ROOT} )/usr/share/cmake/Modules/FindBoost.cmake(177): find_package(Boost QUIET NO_MODULE )/usr/lib64/boost/BoostConfigVersion.cmake(12): if(${PACKAGE_FIND_VERSION_MAJOR}.${PACKAGE_FIND_VERSION_MINOR}.${PACKAGE_FIND_VERSION_PATCH} STREQUAL 1.41.0 )/usr/lib64/boost/BoostConfig.cmake(20): set(Boost_VERSION 1.41.0 )/usr/lib64/boost/BoostConfig.cmake(21): set(Boost_INCLUDE_DIRS /usr/include )/usr/lib64/boost/BoostConfig.cmake(22): set(Boost_INCLUDE_DIR /usr/include CACHE FILEPATH Boost include directory )/usr/lib64/boost/BoostConfig.cmake(24): set(Boost_LIBRARY_DIRS /usr/lib64 )This will then again lead to the same error as before.It seems that cmake absolutely wants to go into /usr/share/cmake/Modules/FindBoost.cmake and then /usr/lib64/boost/BoostConfig.cmake, no matter wheter I set Boost_NO_SYSTEM_PATHS TRUE.Best regards,MichaelOn Tue, Aug 8, 2017 at 10:00 PM, Chris Marsh <> wrote:In your project cmake.And I would not manually set these variablesBoost_DIR /usr/lib64/boost
Boost_INCLUDE_DIR /usr/includeI would let the find_pacakge call do that for you.On 8 August 2017 at 13:56, Michael Bieri <> wrote:Just in the cmake file of my project, or in the cmake file for building CGAL?On Tue, Aug 8, 2017 at 9:48 PM, Chris Marsh <> wrote:You put them before the find_package(Boost REQUIRED) call in your cmake file. You will not need to recompile boost.For example:set(Boost_NO_SYSTEM_PATHS TRUE)set(BOOST_ROOT "/my/boost/boost_1_54_0")find_package(Boost REQUIRED)message(STATUS "Found boost incl: ${Boost_INCLUDE_DIR}")message(STATUS "Boost libs to link: ${Boost_LIBRARIES}")message(STATUS "Found boost lib: ${Boost_LIBRARY_DIRS}")should print your custom boost library pathOn 8 August 2017 at 13:37, Michael Bieri <> wrote:Hi ChrisThanks for your answer. Where exactly should I put those lines, and do I need to recompile CGAL afterwards?Best regards,MichaelOn Tue, Aug 8, 2017 at 9:29 PM, Chris Marsh <> wrote:When compiling against a custom boost with cmake, you can use this in your cmake file to specify the boost directoryset(Boost_NO_SYSTEM_PATHS TRUE)set(BOOST_ROOT "/my/boost/boost_1_54_0")the FindBoost.cmake file will then pickup your custom directoryOn 8 August 2017 at 13:14, Michael Bieri <> wrote:HelloI'm currently installing CGAL on different platforms. Normally, it works just fine. But I have one computer where Boost is not installed into the system, but just compiled in a directory. This Boost works properly in combination with other things I'm building, just not with CGAL.I can compile CGAL using the following Boost-related settings, displayed with ccmake:
Boost_DEBUG OFF
Boost_INCLUDE_DIR /my/boost/boost_1_54_0
Boost_LIBRARY_DIR /my/boost/boost_1_54_0/stage/lib
Boost_SYSTEM_LIBRARY_DEBUG /my/boost/boost_1_54_0/stage/lib
Boost_SYSTEM_LIBRARY_RELEASE /my/boost/boost_1_54_0/stage/lib
Boost_THREAD_LIBRARY_DEBUG /my/boost/boost_1_54_0/stage/lib
Boost_THREAD_LIBRARY_RELEASE /my/boost/boost_1_54_0/stage/lib
CGAL_Boost_USE_STATIC_LIBS OFF
Now, I'd like to compile one of my examples. I get the following error:*******************************************************CMake Error at /usr/lib64/boost/Boost.cmake:536 (message):
The imported target "boost_date_time-static" references the file
"/usr/lib64/lib64/libboost_date_time.a"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib64/boost/Boost.cmake"
but not all the files it references.*******************************************************The error itself is not a surprise, because it's a very old Boost there.Boost-related settings for cmake in my project folder are:Boost_DEBUG OFF
Boost_DIR /usr/lib64/boost
Boost_INCLUDE_DIR /usr/includeWhe I change the variables to my own Boost in ccmake, it will also throw the above error and not save the changes.So I really, really wonder: How do I set Boost properly to compile my own code? (I also tried with environment variables as given in the installation manual, Section 15.7.)Best regards,Michael
- Re: [cgal-discuss] Boost is not found when compiling my own code, (continued)
- Re: [cgal-discuss] Boost is not found when compiling my own code, Michael Bieri, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Chris Marsh, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Michael Bieri, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Jesse Blankenship, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Chris Marsh, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Michael Bieri, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Chris Marsh, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Michael Bieri, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Chris Marsh, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Biswajit Biswas, 08/09/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Michael Bieri, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Chris Marsh, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Michael Bieri, 08/08/2017
- Re: [cgal-discuss] Boost is not found when compiling my own code, Chris Marsh, 08/08/2017
Archive powered by MHonArc 2.6.18.