Re: [CMake] Asking CMake to setup compiler for c++11

On Wed, Oct 21, 2015 at 2:18 PM, Craig Scott wrote: >> CMAKE_MINIMUM_REQUIRED(VERSION 3.1) >> SET(CMAKE_CXX_STANDARD 11) > http://crascit.com/2015/03/28/enabling-cxx11-in-cmake/ Dan, Craig: Thanks that's great news, Chris -- Powered by www.kitware.com Please keep messages on-topic and check

[CMake] Asking CMake to setup compiler for c++11

Hi, Q: What is the "CMake way" to ask that the compiler be setup for c++11? FYI I could not find the answer at https://cmake.org/cmake/help/v3.4/search.html?q=c%2B%2B11 Thank you, Chris -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.

[CMake] CMake way to achieve march=native

Hi, What is the CMake way to get march=native? By "CMake way" I'm looking for something that is somewhat robust, works, doesnt' confuse CMake itself... perhaps even works if/when anyone is going to cross compile, etc. The cross-compile part isn't a requirement... I'm just trying to get you to un

Re: [CMake] Do not build targets whose dependencies are not available

On Tue, Mar 19, 2013 at 3:13 AM, Ansis Māliņš wrote: >> >> Q: Can cmake automatically not build "b" when "a" is not available? > > find_package(a) > if(a_FOUND) > ExternalProject_Add(b PREFIX blabla ...) > endif() Hello, If I understand correctly, this is what just happened: Chris: Is there

[CMake] Do not build targets whose dependencies are not available

Hello, I have a library target ("a") that is a dependency of an executable ("b"). I have many more libraries and many more executable, some with "complex" dependencies on the others. Sometimes target "a" cannot be built either because the user does not want it built or because FIND_PACKAGE faile

Re: [CMake] Please critique my "hello world" CMakeLists.txt and Config.cmake

On Sun, Feb 24, 2013 at 12:37 PM, Alexander Neundorf wrote: >> github links: >> https://github.com/chrisstankevitz/hello >> https://github.com/chrisstankevitz/hello-client > > Maybe we'll start with the old way and get to the new way. Alex, Thank you again. I updated the projects per your teach

Re: [CMake] Please critique my "hello world" CMakeLists.txt and Config.cmake

On Sun, Feb 24, 2013 at 2:20 AM, Alexander Neundorf wrote: > * "export" the target (use the EXPORT option in install(TARGETS)) > * the install this "export", using install(EXPORT ...), this will install a > cmake script file > * include() this export-file in the Config.cmake file > * use configure

[CMake] Please critique my "hello world" CMakeLists.txt and Config.cmake

Hello, Would you please critique my CMakeLists.txt and helloConfig.cmake.in files? I am particularly interested in comments that will help me fix these problems: - In helloConfig.cmake.in, I assume static libraries will be built (".a"). I imaging a better approach would make no assumptions abou

Re: [CMake] Eclipse generator: run/debug configurations

On Sat, Jun 2, 2012 at 7:20 PM, Chris Stankevitz wrote: > When I try to add a breakpoint in the source editor, gdb > complains: The problem was that I did not ask cmake to create a debug build. Fixed that and now eclipse works as expected. Chris -- Powered by www.kitware.com Visit

[CMake] Eclipse generator: run/debug configurations

Hello, Q1: Why doesn't the cmake eclipse generator produce run/debug configurations for the executables in my cmake project? Q2: How can I add run/debug configurations to my eclipse project such that I can run, debug, and set breakpoints in my executable (from within eclipse)? More detail: I am