The standard choice is c++
[eschnigma@manjaro ~]$ c++ --version c++ (GCC) 6.1.1 20160501 Copyright (C)
2016
Free Software Foundation, Inc. This is free software; see the source for
copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
But I've tried enforcing g++ as such:
-DCMAKE_C_COMPILER:FILEPATH=/usr/bin/gcc -DCMAKE_CXX_COMPILER:STRING=/usr/
bin/g++
And that has the same results.
Version:
[eschnigma@manjaro ~]$ g++ --version g++ (GCC) 6.1.1 20160501 Copyright (C)
2016
Free Software Foundation, Inc. This is free software; see the source for
copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
On Wednesday, June 1, 2016 10:05:21 AM EEST Chuck Atkins wrote:
[eschnigma@manjaro build]$ cmake .. -DCMAKE_BUILD_TYPE:STRING="Debug"
This is definitely the reason for no debug symbols. If the compiler is unknown
then
CMake won't know the right flags to pass to generate debug info. The more
important
question though is why the compiler can't be identified. What compiler is
being used?
Can check with /usr/bin/c++ --version ?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
