[Cmake-commits] CMake branch, master, updated. v3.7.0-620-g6eb654c

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1329-g250c3b9

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, next has been updated via 250c3b994e4057baaa713288697cb29eda59de25 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-1327-g39707fb

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, next has been updated via 39707fbe51f914b538aabfa6f02852009f24d370 (commit) via

[cmake-developers] QtAutogen suggestions

Hi. There are some issues with QtAutogen that still bother me and that I would like to change. 1) Most files get generated in ${CMAKE_CURRENT_BINARY_DIR}/${TARGETNAME}_automoc.dir Is the ".dir" suffix neccessary? I think is should be removed. 2) Moc files that are manually included by a

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

Sorry, bad link in that last email. The try_compile() docs I meant to link to are here: https://cmake.org/cmake/help/latest/command/try_compile.html#other-behavior-settings On Sat, Nov 26, 2016 at 9:23 AM, Craig Scott wrote: > Sorry, I misunderstood. I had a look

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

Sorry, I misunderstood. I had a look through the check_cxx_source_compiles() implementation and it basically forwards through to a try_compile() call. Looking at the docs for try_compile() , it says only the following are passed through to the temporary CMake project created for the test

[CMake] v3.7.0 - archive_cryptor_private.h - compile error

Hello, I receive the following when building: [ 40%] Building C object Utilities/cmlibarchive/libarchive/CMakeFiles/cmlibarchive.dir/archive_cryptor.c.o In file included from /home/nathan/development/cmake/Utilities/cmlibarchive/libarchive/archive_cryptor.c:32:0:

Re: [CMake] Executing python though CMake and linking libraries

Hmmm… I get the same error if I use absolute paths. I don’t really understand why the shell environment used to launch CMake and make is not being inherited by the executed commands. Kit > On 25 Nov 2016, at 13:23, tonka3...@gmail.com wrote: > > Hey, > > I think your actual working

Re: [CMake] Executing python though CMake and linking libraries

Hey, I think your actual working directory is wrong. I would recommend to use absolute paths for the python interperter (there is a find_package module for the interpreter) and maybe also for your script. The custom command support a workingdirectory variable as far as i know. Hope that help

Re: [CMake] [cmake-developers] C++11/C++14 doesn't work in check_cxx_source_compiles

but it does not set/add the required library > Am 24.11.2016 um 22:01 schrieb Craig Scott : > > You might also need to set CMAKE_CXX_EXTENSIONS to OFF (it's ON by default). > This controls which c++ library is linked for some compilers, with clang and > gcc being two

[CMake] Executing python though CMake and linking libraries

I have a Cmake custom target which runs a python script: add_custom_target(run COMMAND python myscript.py ) And the script myscript.py imports a Compiled library import myproj.mylilb where mylib is actually a C++ library generated with python bindings