Re: [CMake] ctest: building test in parellel

to now. However ctest now appears to be building more than just the tests. Its not rebuilding everything just some of the libraries. make on its own seems to respect the dependencies and only rebuild what is required unless I've run ctest. On 27 June 2017 at 13:03, Eric Noulard wrote:

Re: [CMake] ctest: building test in parellel

Sadly -j does not appear to help. I have also tried setting the gmake MAKEFLAGS environment as well. On 27 June 2017 at 12:34, Craig Scott wrote: > Does the -j option to ctest not do what you want? > > On Tue, Jun 27, 2017 at 9:32 PM, Damian Dixon > wrote: > >> Hi, >

[CMake] ctest: building test in parellel

Hi, Is there anyway to build tests in parallel when using ctest? I am generating makefiles on Linux. Part of the reason I am asking this is that if I pre-build the test for some unknown reason ctest rebuilds the source files. I am currently using cmake 3.8.0. Thanks Damian -- Powered by

[CMake] CMake Project Generation Speedup

Hi all, We are still in the process of switching our large Make-based build to CMake. One of the issues we're running into is the time it takes to reparse and regenerate the CMake project (whether ninja, VS, or make) after touching any CMake file. To give you an idea, we have about 1000 targets an

Re: [CMake] Cmake 3.5.0 and Fortran submodule cannot be built

I hope we’ll see CMake support for submodules soon. Submodules are now supported by released versions of the Cray, IBM, and Intel compilers and by the pre-release GNU Fortran compiler version 6.0.0, which is expected to release in mid-April. Damian On Mar 23, 2016, at 1:12 PM, Brad King

Re: [CMake] FORTRAN name mangling

> On Jan 11, 2016, at 11:31 AM, Zaak Beekman wrote: > > > So if I require Fortran 2003 for our fortran codes then this whole ?fortran > name-mangling? thing becomes a moot point, i.e. I do not have to actually > worry about it at all for our project. Just have to keep the C header > consiste

Re: [CMake] CMake 3.3 and 3.2 bootstrap fails on OS X Yosemite

ld adjust the provided GCC build script [2] to apply the patch, but it’s kind of a lot to ask people to install a patched GCC in addition to the GCC they might already have on their system. Damian [2] https://github.com/sourceryinstitute/opencoarrays/blob/master/install_prerequisites/buildgc

Re: [CMake] CMake 3.3 and 3.2 bootstrap fails on OS X Yosemite

rror with cmake-3.3.2.tar.gz. Damian -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support:

[CMake] CMake 3.3 and 3.2 bootstrap fails on OS X Yosemite

https://cmake.org/Bug/view.php?id=15762). Damian Rouson, Ph.D., P.E. President, Sourcery Institute http://www.sourceryinstitute.org +1-510-600-2992 (mobile) g++ -I/Users/rouson/Code/sourceryinstitute/AdHoc/src/cmake/bug-/cmake-3.3.0/Bootstrap.cmk -I/Users/rouson/Code/sourceryinstitute/AdHoc/src

Re: [CMake] Unreliable Find*.conf

rything without any hint in the find-module, so long as I set CMAKE_PATH_PREFIX. I erased all cmake-caches I could find from the source tree and switched to out-of-source build - but still, cmake can find the TS3 library on its own. Is there some hidden cache elsewhere that I need to erase?

Re: [CMake] Unreliable Find*.conf

brary filenames as find_library() has. Regards, Damian Philipp -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please vis

[CMake] Unreliable Find*.conf

n) > > # Combine into output information > set(ts3sdk_INCLUDE_DIRS ${ts3sdk_INCLUDE_DIR}) > set(ts3sdk_LIBRARY_DIRS ${ts3sdk_LIBRARY_DIR}) > > message(STATUS "ts3sdk headers found in " ${ts3sdk_INCLUDE_DIRS}) > message(STATUS "ts3sdk libraries used: " ${ts