Forgot to mention:
~> cmake --version
cmake version 3.5.0
Le 2017-03-13 19:33, houssen a écrit :
Hello,
I do NOT use /usr/bin/g++ that is installed in the system (long story
- don't ask why).
I compiled gcc from source and installed it in
/my/path/local/bin/g++.
Now I need to check for tup
Hello,
I do NOT use /usr/bin/g++ that is installed in the system (long story -
don't ask why).
I compiled gcc from source and installed it in /my/path/local/bin/g++.
Now I need to check for tuple with CHECK_INCLUDE_FILE_CXX : it fails !
Still failing if:
1. I export CPLUS_INCLUDE_PATH to poin
I'm finding the PUBLIC_HEADER target property to be quite convenient for
clarity's sake. Specifically it spells out quite unambiguously that "hey,
these are the headers I want to be published" while at the same time providing
locality to the export details with "PUBLIC_HEADER DESTINATION foo" a
Below is my current cmake script for building libc++. There are several things
about this script I would like to cleanup, but the really big one is fact that
I have to download libcxx and libcxxabi twice. This is because libcxx,
libcxxabi and llvm have a circular dependency (each relies on the o
At the end of the day, here is what I did:
1) create a development Centos 5.5 machine
2) on the dev machine, I compiled gcc 4.9.3 from sources, installed it
locally and updated the build system (cmake, etc..) with only local
builds, if possible from source. By exploiting LD_LIBRARY_PATH, I l
