Re: [CMake] Known issues with Xcode 6.x and CMake

> On Oct 19, 2015, at 7:01 AM, Gregor Jasny via CMake wrote: > > Hello, > > On 17/10/15 18:28, Michael Jackson wrote: >> Are there any known issues with Xcode 6.4 and CMake 3.3.x? I ask because in >> our project when we generate the Xcode project we end up with 2 or 3 >>

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-798-gd861762

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 d861762709fdf5bd01be4b83e4701194203c646a (commit) via

[CMake] Python project using Cmake

Hello All, I am new to cmake and its build and ctest system. I read some where that cmake default look for c++ compiler and we need to modify/configure the cmake to recongize the python files. I googled for the same but I couldn't find any concrete and complete example. Any pointers in this

Re: [CMake] ExternalProject_Add and proxy

Hello Denis! Thank you for your answer. Actually, there is no login and no password. It's an academic proxy. So the initial syntax of http_proxy should to be correct. Cédric - Mail original - > De: "D. Barbier" > À: "Cedric Doucet" > Cc:

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-340-g56cec75

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 56cec75058b1980ead58ddda0c371a783547acec (commit) via

[Cmake-commits] CMake branch, release, updated. v3.4.0-rc1-26-g498db9b

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, release has been updated via 498db9b9bcfdf391ff89ffc0b273a65d0bc1bd7e (commit) from

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-811-g998a7db

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 998a7db7d498dc96407ad960f24d5294859d889b (commit) via

Re: [CMake] ExternalProject_Add and proxy

On 2015-10-21 14:58 GMT+02:00 Cedric Doucet wrote: > > Hello, > > I try to download a library with ExternalProject_Add. > The URL is correct and the CMake script works well, except when there is a > proxy to define. > > The URL is : http://bitbucket.org/eigen/eigen/get/3.2.4.tar.gz > > After

Re: [CMake] Python project using Cmake

What are you trying to do? Are you trying to build Python C extensions? If so then the FindPythonLibs module will help you in that regard. It will determine if the Python development files are installed and populate variables with the necessary paths to provide to link_directories and

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-813-g8ab1833

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 8ab1833c2ad99fa882b7aa85ac87ded78c580576 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-816-gedf57f3

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 edf57f39262a38c17ba78501ebda5ac7eb23fe4e (commit) via

Re: [CMake] Creating relocatable packages

Great! Always happy to help! On Tue, Oct 20, 2015 at 9:58 AM, Zac Bergquist wrote: > Yes, that was exactly what I needed. > > Now my installed targets file has IMPORTED_LINK_INTERFACE_LIBRARIES "PCAP" > instead of an absolute path, and the FindPCAP.cmake module kicks in

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-849-gc3d33f3

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 c3d33f3b0d9341d1a5927382ff58e6ba4baa330f (commit) via

Re: [CMake] Python project using Cmake

Hi Matthew Keeler, Thanks for your quick reply. My project is a pure python project. I wanted to use cmake and ctest for testing my individual python modules. Later on, I might have some "tcl" scripts and may be some c++ sources in the same project. It would be great, if you could share your

[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

[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:

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

Something like CMAKE_MINIMUM_REQUIRED(VERSION 3.1) SET(CMAKE_CXX_STANDARD 11) I think. On Wed, Oct 21, 2015 at 12:43 PM, Chris Stankevitz wrote: > 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 >

[Cmake-commits] CMake annotated tag, v3.4.0-rc2, created. v3.4.0-rc2

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 annotated tag, v3.4.0-rc2 has been created at 2b848180d46b682ad1074f740a2b01c80d4fca4a (tag) tagging

[CMake] using source files in build directory

Hello All, Is it possible to have CMake use source files in some particular order that are placed in the out-of-source build directory? This is allows for the convenience of having multiple builds in different build directories due to a few file changes while preserving the files themselves?

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc2-826-g7b38cda

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 7b38cda3bc92ab002b19020a1c201552d039a6fc (commit) via

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

> -- Forwarded message -- > From: Dan Kegel > To: Chris Stankevitz > Cc: cmake > Date: Wed, 21 Oct 2015 12:54:44 -0700 > Subject: Re: [CMake] Asking CMake to setup compiler for c++11 > Something like > >

[cmake-developers] [ANNOUNCE] CMake 3.4.0-rc2 is now ready!

I am proud to announce the second CMake 3.4 release candidate. Sources and binaries are available at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.4 Release notes appear below and are also published at

[CMake] [ANNOUNCE] CMake 3.4.0-rc2 is now ready!

I am proud to announce the second CMake 3.4 release candidate. Sources and binaries are available at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.4 Release notes appear below and are also published at

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc2-828-g9d230d9

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 9d230d94b91625ed2edaae73649b0371013cf54a (commit) via

Re: [cmake-developers] Add command line options for deprecation message control

I think having local CMAKE_WARN_DEPRECATED/CMAKE_ERROR_DEPRECATED vars can be left as specific to the message() command (and perhaps other IssueMessage callers as deemed appropriate per-case). Otherwise we should just have one global setting. Okay that sounds good to me, makes the

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

Re: [cmake-developers] CMAKE_Fortran_SIMULATE_VERSION

On 10/21/2015 05:26 AM, nun...@iol.pt wrote: > How is the CMAKE_Fortran_SIMULATE_VERSION created? Take a look at these files: Modules/CMakeDetermineCompilerId.cmake Modules/CMakeFortranCompilerId.F.in: The INFO:simulate_version[] strings are used to extract the value from a binary compiled

Re: [cmake-developers] [Patch] Documentation file(GLOB): ordering note

On 10/20/2015 05:03 PM, Ruslan Baratov via cmake-developers wrote: > Add a note that order of files is not defined Thanks, applied: Help: Document that file(GLOB*) order is undefined https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5a208f83 -Brad -- Powered by www.kitware.com Please

[CMake] ExternalProject_Add and proxy

Hello, I try to download a library with ExternalProject_Add. The URL is correct and the CMake script works well, except when there is a proxy to define. The URL is : http://bitbucket.org/eigen/eigen/get/3.2.4.tar.gz After having set http_proxy=http://proxy.name.fr:1234

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-308-ge2d4bfe

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 e2d4bfef3fe24ba5846abbb2dc2c2e0ef58a21f5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-312-g8bcf2c8

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 8bcf2c81fc2a2bc458d54f9d5dbd40b49e5b993e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-317-g740f85a

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 740f85a204d7a837e3ad408a79992f6a9c0b000c (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-306-gf1de724

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 f1de724f41a516574f22d2b0e61ebf4b6d65c601 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-791-g6a889f1

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 6a889f151253e98bb7cbe7d500f07c88021a8bce (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-310-g196de9d

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 196de9d14d281103e0ee5c36e9dfd39504804aeb (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-335-g9206120

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 9206120e30d91389470aa0908965103dc301bbae (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-323-gd31d92b

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 d31d92bf1d8b13ddff2c85c1fd380519867b788c (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-338-ge4b7d5a

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 e4b7d5afde91efafb59749a0a513732a089a6f0a (commit) via

[Cmake-commits] CMake branch, release, updated. v3.4.0-rc1-25-g2ad1fed

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, release has been updated via 2ad1fed8ee1ddcee831ffe5b70f2abab52430b70 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-795-gf3ec156

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 f3ec1567ed0a0980074091afcddf5a6c8a1b015d (commit) via

[CMake] CMake add_definitions string definitions fails on OS X

Hi all! I am using CMake and g++ on OS X 10.10. My problem is following: in CMakeLists.txt I add line: add_definitions(-DPROJECT_ROOT="${CMAKE_CURRENT_SOURCE_DIR}/../..") When I try to use PROJECT_ROOT in source code I can not build it. It says error: expected expression std::cout <<

[cmake-developers] CMAKE_Fortran_SIMULATE_VERSION

Hi All, I am trying to track down a problem related to the assignment of values to the MSVC_VERSION variable and I have a question: How is the CMAKE_Fortran_SIMULATE_VERSION created? which source file should I look for? I know about the file CMakeFortranCompiler.cmake.in but it is not

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-782-g3df8be1

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 3df8be1826ac49fb99a495288873bb02f6690e38 (commit) via

[CMake] cmake.exe build type from cmd

Hello, Using CMake 3.3 on Windows 7 platform with VS2012. To build software I run; cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -G "Visual Studio 11" /path/to/source msbuild /m /p:Configuration=RelWithDebInfo INSTALL.wcxproj To help developers I would like to create a couple of scripts. Does