Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMake version and Boost version (e.g.upgrading to boost 1.66 or later will need CMake 3.11) #103

Closed
KrisThielemans opened this issue Mar 18, 2018 · 7 comments

Comments

@KrisThielemans
Copy link
Member

KrisThielemans commented Mar 18, 2018

From the CMake mailing list

RE: Can't find Boost with Visual Studio 2017
From: Volker Enderlein
Boost changed its naming scheme starting from version 1.66. So its not your fault but the FindBoost.cmake does not know how to handle the new scheme. Try to use one of the 3.11.0-rc[1-3] versions that has the proper naming scheme handling of 1.66 or use the 1.65.1 that is the last version with the old naming scheme.

@KrisThielemans KrisThielemans changed the title upgrading to boost 1..66 or later will need CMake 3.11 upgrading to boost 1.66 or later will need CMake 3.11 Mar 18, 2018
@DANAJK
Copy link
Contributor

DANAJK commented Mar 19, 2018

Richard came to help last week but I am still having trouble. I realise now there was an error in an environment variable (the 'R' was missing in 'MATLAB_R2017' so I have decided to rebuild from scratch.

I noticed the messages below go past when the build started, though I was expecting it to use the boost 1.66 that should be on my system, and not start downloading 1.63 .

Anyway, my question is more basic. I want to check the cmake configuration and I can run the cmake-gui. However, it is not obvious how to answer: 'Where is the source code' and 'Where to build the binaries'. I'm sure it is obvious to those of you who develop everyday, but to the novice there is a bewildering array of folders with 'build' in the name.

531:~/devel/build$ make -j2
Scanning dependencies of target FFTW3
Scanning dependencies of target Boost
[ 1%] Creating directories for 'FFTW3'
[ 2%] Creating directories for 'Boost'
[ 4%] Performing download step (download, verify and extract) for 'Boost'
[ 4%] Performing download step (download, verify and extract) for 'FFTW3'
-- Downloading...
dst='/Users/davidatkinson/devel/build/downloads/FFTW3/fftw-3.3.5.tar.gz'
timeout='none'
-- Using src='http://www.fftw.org/fftw-3.3.5.tar.gz'
-- Downloading...
dst='/Users/davidatkinson/devel/build/downloads/Boost/boost_1_63_0.zip'
timeout='none'
-- Using src='http://downloads.sourceforge.net/project/boost/boost/1.63.0/boost_1_63_0.zip'

@rijobro
Copy link
Contributor

rijobro commented Mar 22, 2018 via email

@KrisThielemans
Copy link
Member Author

KrisThielemans commented Mar 22, 2018 via email

@KrisThielemans KrisThielemans changed the title upgrading to boost 1.66 or later will need CMake 3.11 CMake version and Boost version (e.g.upgrading to boost 1.66 or later will need CMake 3.11) Dec 8, 2018
@KrisThielemans
Copy link
Member Author

In fact, for a particular CMake version, it "knows" only about compilers and libraries in existence at the time that CMake version was released. Therefore, CMake's Find*.cmake will contain logic for those versions only.

Example: CMake 3.7 only knows about to Boost 1.63.0;1.63;1

You can tell FindBoost.cmake to find more recent stuff, but if the conventions of the library changed (as in the top-message of this issue), then CMake cannot know, and it will fail.

Conclusion: we need to recommend to use the latest CMake, and update our own CMake versions (of course, skipping the ones that we know have problems!).

@DANAJK
Copy link
Contributor

DANAJK commented Dec 9, 2018

A dependency of the dependency manager ...?

@KrisThielemans
Copy link
Member Author

:-)

paskino pushed a commit to paskino/SIRF-SuperBuild that referenced this issue Oct 25, 2021
@KrisThielemans
Copy link
Member Author

@paskino I think this can be closed now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants