[CMake] CMake 3.9.0 Windows zip file shows wrong version

Hi all, The CMake 3.9.0 Windows zip file gives the wrong version. Here’s a snippet from my AppVeyor logs [1]: set CMAKE_URL="https://cmake.org/files/v3.9/cmake-3.9.0-win64-x64.zip; appveyor DownloadFile %CMAKE_URL%

Re: [CMake] Advice on converting legacy project to modern CMake

On 2017-08-07 11:35- Björn Blissing wrote: 1. Which version if CMake should I target? I.e. Which version should I require in my cmake_minimum_required() statement? I would suggest either cmake_minimum_required(VERSION 3.6.2 FATAL_ERROR) or cmake_minimum_required(VERSION 3.7.2

[CMake] CMake + Gradle for Android

Right now I have custom targets set to execute the "ant release" command after my native targets are built. Part of that command involves copying *.so files to the libs/armeabi-v7a directory so they get packaged in an APK. When switching to gradle, I have two options: 1. Gradle drives CMake:

Re: [CMake] CMake + Gradle for Android

Either option can work fine. Disclosure: I work on Android Studio and was the one that added CMake support. Option (1) is the way it's designed to work and we're working toward getting rid of the need for the CMake fork. I can't really say when that will happen but if you can get away with an

Re: [CMake] CMake + Gradle for Android

1) There is a folder created for each ABI under the project module folder (so unique per module per ABI) 2) Gradle doesn't specify language level though you can choose to specify it yourself from the build.gradle. This doc does a pretty good job of explaining which variables are set by Gradle:

Re: [CMake] CMake + Gradle for Android

Thanks Jom Honestly, I prefer option 1 to work simply because that's how Google's officially supporting CMake. But it also has debugging which is the #1 reason for me. However, I'd like to understand a lot more about how the integration really happens. For example, I have these questions: 1)

Re: [CMake] Coverage support

Am 2017-08-07 11:06, schrieb Clément Gregoire: I usually stop reading Cmakelists.txt as soon as I see this set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -pedantic -pthread -g -O0 -fprofile-arcs -ftest-coverage") The pthread thing there is likely wrong anyway, and the -Wall is entirely

Re: [CMake] Advice on converting legacy project to modern CMake

Am 2017-08-07 11:57, schrieb Björn Blissing: Hi Eike, 3. Some of my legacy projects have all source in the same directory, i.e. both source and header files are in the same directory. Others have both private and public headers in the same directory. How do I handle this with

Re: [CMake] Coverage support

I usually stop reading Cmakelists.txt as soon as I see this set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -pedantic -pthread -g -O0 -fprofile-arcs -ftest-coverage") Also you need to use the SETUP_TARGET_FOR_COVERAGE for every single test target, which seems to be a difficult to scale on big

[CMake] with cmake-3.9 my testprj breaks, I need to add "add_executable(Qt4::rcc IMPORTED)"

Hi, I have a cmake test project that builds a "hello world" with our cross toolchain. There are selfmade TOOLCHAINFILES for the targets. They define QT variables like: set(BT_QT_4_7_3_PATH.../taget/Qt-4.7.3) set(QT_BINARY_DIR${BT_QT_4_7_3_PATH}/bin) set(QT_LIBRARY_DIR

[CMake] Advice on converting legacy project to modern CMake

Hi, I have some legacy projects which I intend to update to modern CMake. The documentation is good but do not really cover "best practices". So I have some questions which I hope some of you could help to answer: 1. Which version if CMake should I target? I.e. Which version should I require

Re: [CMake] Advice on converting legacy project to modern CMake

Am 2017-08-07 11:35, schrieb Björn Blissing: Hi, I have some legacy projects which I intend to update to modern CMake. The documentation is good but do not really cover "best practices". So I have some questions which I hope some of you could help to answer: 1. Which version if CMake should I

[CMake] Coverage support

Hi, I'm a bit stuck when trying to add coverage reports to Cmake (gcov + lcov) as I can't figure out what is the best (idiomatic) way to do it. So far here are the ways I know of : - setting the CMAKE_LANG_FLAGS based on a boolean + scan all files / run gcov on it : would like to avoid this - same

Re: [CMake] Coverage support

> > I usually stop reading Cmakelists.txt as soon as I see this > > > > set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -pedantic -pthread -g -O0 > > > -fprofile-arcs -ftest-coverage") > > > > The pthread thing there is likely wrong anyway, and the -Wall is entirely > optional. The other things are

[CMake] nagfor, Ninja, and Missing variable is: CMAKE_Fortran_PREPROCESS_SOURCE

Hello, I was trying to build my Fortran project with nagfor using the Ninja generator. I ran into the below error. I am using cmake version 3.9.0. I found a discussion of a similar error at http://public.kitware.com/pipermail/cmake/2016-December/064710.html If I add the following line for the

[CMake] HOWTO cmake compatiblity?

Hi, I like to learn how you use cmake in environments were reproducibility is an issue. Background: We are used to simply install cmake in default $PATH, but I noticed cmake is not backward-compatible. Of course this is not surprising, it is really complex with many nice features and of

Re: [CMake] HOWTO cmake compatiblity?

Steffen Dettmer wrote: […] So far I think we need to install cmake into a versionized directory and invoke it: v1.0.0/bin/cmake -DTOOLCHAIN=v1.0.0/target1.cmake and maybe remove cmake from PATH to ensure a failure if accidentally calling "cmake". What do you think? Having multiple

[CMake] with 3.9 my testprj breaks: mylib_autogen/include: No such file or directory

Hi, I made a fix for [1] and tested cmake master branch, but noticed that this cmake version does not compile my test project anymore (v.3.8.2: OK; v3.9.0: FAIL). There is an include path to $buildir/$subproject/mylib_autogen/include as -I for g++, but this directory does not exist and I get:

Re: [CMake] HOWTO cmake compatiblity?

On Mon, Aug 7, 2017 at 3:44 PM, Rolf Eike Beer wrote: > Steffen Dettmer wrote: >> So far I think we need to install cmake into a versionized >> directory and invoke it: >> >> v1.0.0/bin/cmake -DTOOLCHAIN=v1.0.0/target1.cmake >> >> and maybe remove cmake from PATH to ensure a

[CMake] Yet another CMake 3.9 CUDA issue

Hi, after solving a different issue (lack of .NET 3.5 Framework causing the CUDA MSBuild component to not work, discussion thread "Visual Studio with CUDA does not work in 3.9") and getting good results (parallel CUDA builds, yay!), I now wanted to try CMake 3.9 on a different machine, but no

Re: [CMake] Coverage support

Am 2017-08-07 09:57, schrieb Clément Gregoire: Hi, I'm a bit stuck when trying to add coverage reports to Cmake (gcov + lcov) as I can't figure out what is the best (idiomatic) way to do it. So far here are the ways I know of : - setting the CMAKE_LANG_FLAGS based on a boolean + scan all files

Re: [CMake] Coverage support

07.08.2017, 17:24, "Clément Gregoire" : >> I usually stop reading Cmakelists.txt as soon as I see this >> >> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -pedantic -pthread -g -O0 >> -fprofile-arcs -ftest-coverage") >> >> The pthread thing there is likely wrong anyway, and the

Re: [CMake] Coverage support

  07.08.2017, 20:50, "Clément Gregoire" :This is mainly why I started this thread, I want to know the best way to do this without using those variables.CMAKE_lang_FLAGS is a pain as soon as someone wants to use add_subdirectory (be it to add an external project or your project

Re: [CMake] with 3.9 my testprj breaks: mylib_autogen/include: No such file or directory

On 08/07/2017 09:01 AM, Steffen Dettmer wrote: > this cmake version does not compile my test project anymore > (v.3.8.2: OK; v3.9.0: FAIL). There is an include path to > $buildir/$subproject/mylib_autogen/include as -I for g++, but > this directory does not exist and I get: > > cc1plus: error

Re: [CMake] CMake CUDA 3.8+/9 support as a first class language with out Visual Studio Support... err what?

It is great to hear that you have been able to resolve the compilation issues with CMake, though it is very weird and worry some that only formatting your machine would resolve the issue. 1) The error code you are getting (46-cudaErrorDevicesUnavailable ) generally means that another CUDA program

Re: [CMake] Coverage support

This is mainly why I started this thread, I want to know the best way to do this without using those variables. CMAKE_lang_FLAGS is a pain as soon as someone wants to use add_subdirectory (be it to add an external project or your project being used in another) or a user wants to change the value.

Re: [CMake] with cmake-3.9 my testprj breaks, I need to add "add_executable(Qt4::rcc IMPORTED)"

Did this work pre CMake 3.9? On Mon, Aug 7, 2017 at 8:49 AM, Steffen Dettmer wrote: > Hi, > > I have a cmake test project that builds a "hello world" with our > cross toolchain. There are selfmade TOOLCHAINFILES for the > targets. They define QT variables like: > >

[Cmake-commits] CMake branch, master, updated. v3.9.0-437-gb17b6db

_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170807) +set(CMake_VERSION_PATCH 20170808) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] Linking Apple frameworks

On 8/7/17, Brad King wrote: > On 08/05/2017 07:58 PM, Craig Scott wrote: >> target_link_libraries(foo PRIVATE "-framework AppKit") >> >> Strangely, with the library quoted as above, the embedded space >> is not escaped, leading to the (desirable but surprising) result >

[Cmake-commits] CMake branch, master, updated. v3.9.0-436-g3a0ef7a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 3a0ef7ac1a50383331f92a19926682d5c1f2682a (commit) via

Re: [cmake-developers] Linking Apple frameworks

On 08/05/2017 07:58 PM, Craig Scott wrote: > target_link_libraries(foo PRIVATE "-framework AppKit") > > Strangely, with the library quoted as above, the embedded space > is not escaped, leading to the (desirable but surprising) result Link flags starting in `-` are treated as a raw part of

Re: [cmake-developers] C++ IDE

QtCreator is nice. --- Jean-Michaël Celerier http://www.jcelerier.name On Sun, Aug 6, 2017 at 10:57 PM, Rolf Eike Beer wrote: > Am Sonntag, 6. August 2017, 17:52:13 schrieb Ivam Pretti: > > Can you recomend an IDE to code in C/C++? > > KDevelop. > -- > > Powered by