Re: [CMake] General cross platform stating place

Hi, On Monday 07 September 2015 23:47:35 Aaron Gray wrote: > cmake_minimum_required(VERSION 2.6) Just as a side note: if you need to support cmake 2.6, that's fine. However, if you are starting a new project and do not *need* to limit yourself to cmake 2.6, develop for a cmake version that as

Re: [CMake] CMake + MPI

Hi Nico, I just use find_package(MPI REQUIRED) and use the given MPI_CXX_LIBRARIES and MPI_CXX_INCLUDE_PATH. Recent mpi wrappers should support support interspection. Regards, Andreas Am 08.09.2015 um 13:01 schrieb Nico Schlömer: Hi everyone, When it comes to compiling and linking, the MPI

[cmake-developers] [CMake 0015730]: foreach() mis items from list when brackets are unclosed

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15730 == Reported By:nmeunier Assigned To:

[CMake] CMake + MPI

Hi everyone, When it comes to compiling and linking, the MPI world is quite a mess. Sometimes, vendors make you link and include certain libraries/directories, sometimes you are supposed to simply use a compiler wrapper, often both. What's the recommended way of dealing with MPI in CMake? Do you

[Cmake-commits] CMake branch, next, updated. v3.3.1-2785-gf3175f9

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

[Cmake-commits] CMake branch, master, updated. v3.3.1-1102-g70ea1d9

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

[Cmake-commits] CMake branch, master, updated. v3.3.1-1098-g4da3315

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

[Cmake-commits] CMake branch, master, updated. v3.3.1-1091-g20b7e79

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

[Cmake-commits] CMake branch, master, updated. v3.3.1-1089-g9290168

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

Re: [CMake] CMake [nmake target] is adding backslash at end of cd command

On 9/4/2015 10:17 AM, André Netzeband wrote: > I have a very strange issue with generated nmake makefiles from cmake 3.3.1 Is this problem new in 3.3 or are you just reporting this as the version you are using? > In a very complex project with many sub-cmake files (Ogre3D) the > generated nmake

[Cmake-commits] CMake branch, next, updated. v3.3.1-2787-g975e550

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

Re: [CMake] CMake + MPI

The only exception to that (which I am aware of) is if you are on a CRAY system where the MPI (and BLAS and LAPACK) are baked into the compiler wrappers (cc, ftn, etc). In those situations, you actually do not want to run find_package(MPI) or it will throw errors. Tim - Original Message

[CMake] Tweaking/disabling timeout for "Check for working CXX compiler"

Hi! FreeBSD project use userspace qemu emulation to cross-build packages for some architectures, namely arm. This worked great for most packages, however ones using cmake tend to fail randomly. I couldn't reproduce these failures, but after we've updated cmake to 3.3.1 which is more verbose, the

[Cmake-commits] CMake branch, master, updated. v3.3.1-1103-g0e7f34c

_VERSION_MINOR 3) -set(CMake_VERSION_PATCH 20150908) +set(CMake_VERSION_PATCH 20150909) #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.3.1-2792-g923d2ba

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