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

2015-09-08 Thread Dmitry Marakasov
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 c

Re: [CMake] CMake + MPI

2015-09-08 Thread Tim Gallagher
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 --

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

2015-09-08 Thread Brad King
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

Re: [CMake] CMake + MPI

2015-09-08 Thread Andreas Naumann
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] CMake + MPI

2015-09-08 Thread Nico Schlömer
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

Re: [CMake] General cross platform stating place

2015-09-08 Thread Johannes Zarl-Zierl
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 n