[CMake] CMake implicit behaviour change between 3.2.2 and 3.3.1

Hi list, I recently upgraded from CMake-3.2.2 to 3.3.1 (well, Gentoo did). I notice the following change. From time to time I cross compile some CMake projects against an Arm chroot. I (admittedly) do not use a toolchain file, but use the following invocation:

Re: [CMake] CMake, QT5 and cross compilation

On Thu, Dec 17, > > So, here is my question: How can I overwrite the moc-executable (and uic > etc) path to use another moc version than the one found by the > find_package mechanism? If I use the moc which is part of my Linux host > PC rather than the arm compiled moc in the Raspberry file

Re: [CMake] Tests with assert and Release build type

On Fri, Dec 18, 2015 at 9:55 AM, Magnus Therning wrote: > > I'm sure I'm not the first one to run into the conflict between a desire > to test the code shipped to customers and the desire to at the same time > define NDEBUG to make sure tests don't have their `assert` turned

Re: [CMake] Cross Compilation & Source file generators

Another "outside the box" solution that I have had success with is as follows (Note this solution will only work with Linux): You can use the Linux binfmt_misc driver to execute non-native executables through an interpreter. If you google for qemu binfmt wrapper, you'll find various suitable

Re: [CMake] best way of parsing test results from ctest + valgrind

On Tue, Mar 1, 2016 at 8:15 PM, Aaron Boxer wrote: > Hello, > I am just getting started on using valgrind memory analysis for my tests. > When I run ctest with nightly memory check, I get an XML document, but it > is very hard to read the results. What is the best way of

Re: [CMake] CMake 3.7.2 and parallel builds

On Mon, Jan 30, 2017 at 9:38 AM, Nils Gladitz wrote: > > I don't know how to do this with the generic dashboard targets ... > assuming no one else does either you could give CTest script mode a try > (ctest -S). > In script mode the ctest_build() command has a FLAGS option

[CMake] CMake 3.7.2 and parallel builds

I've recently upgraded to CMake 3.7.2 (and gnu make-4.2.1). Now, when I execute 'make -j5 NightlyBuild', I get the following new (to me) warning: "gmake[4]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule." If I downgrade make back to the previous version, 4.1-r1 (the -r1

Re: [CMake] CMake 3.7.2 and parallel builds

On Sun, Jan 29, 2017 at 9:53 AM, Nils Gladitz wrote: > FWIW I don't think -j does anything when you build the NightlyBuild target > given that that make invocation is not the one directly performing the > actual build. > The only command being run by the NightlyBuild

Re: [CMake] CMake 3.7.2 and parallel builds

Hey Paul On Sat, Jan 28, 2017 at 10:43 AM, Paul Smith wrote: > My suspicion is that somehow the recursion is invoking an older version > of make. In GNU make 4.2 the jobserver interface was stabilized and > published, so that other build tools could take advantage of it

Re: [CMake] CCACHE_DIR Environment Variable

On Thu, Jan 19, 2017 at 4:44 PM, David Lind wrote: > That’s not the issue. The issue is telling ccache where to place it’s > cache files. If I compiles for toolchain X, Y and X, I need to set > CCACHE_DIR accordingly. Otherwise the cache will be useless. > >

Re: [CMake] libsndfile in winodws

On Thu, Mar 2, 2017 at 9:14 AM, Dave Flogeras <dfloger...@gmail.com> wrote: > > Just my 0.02, but if I recall Eric doesn't (or didn't) support building > directly on Windows. > > Pardon me, that should be Erik -- Powered by www.kitware.com Please keep messages on-topic an

Re: [CMake] libsndfile in winodws

On Thu, Mar 2, 2017 at 8:47 AM, aishwarya selvaraj < aishwaryaselvaraj1...@gmail.com> wrote: > @Dan Liew > Thanks for your feedback. > Yes I was trying to proceed in that direction . > Did you find any links which could be useful ? > could you kindly share them ? > Thanks > > Running a

[CMake] COMPONENT question

Hi, are static libraries able to be added to a component? The following minimal example doesn't work as I expected: CMAKE_MINIMUM_REQUIRED( VERSION 3.0.0 ) PROJECT( foo ) ADD_LIBRARY( foo foo.c ) INSTALL( TARGETS foo ARCHIVE DESTINATION lib RUNTIME DESTINATION bin

Re: [CMake] COMPONENT question

Iosif, that's exactly it, I was not paying attention to the [ ] in the docs! Thanks for your help. On Mon, Oct 31, 2016 at 2:57 PM, iosif neitzke < iosif.neitzke+cm...@gmail.com> wrote: > Try something like: > INSTALL( TARGETS foo ARCHIVE DESTINATION lib COMPONENT bar >

[CMake] PROPERTIES VERSION bug in windows DLL major.minor version

Hi, I noticed that on an older (3.2.2) release I was using with Win7, the behaviour described about automatically parsing VERSION major.minor and putting it into the DLL image version wasn't behaving correctly. It seemed it was applying the VERSION from the first shared library in my project, to

[CMake] FindThreads and toolchains

I am using CMake 3.7.2 and playing around with the FindThread finder. The following simple CMakeLists.txt works fine on various compilers: GCC, clang, MSVC (tried 2013 and 2015). CMAKE_MINIMUM_REQUIRED( VERSION 3.1 ) ADD_EXECUTABLE( mythread main.cpp ) SET( THREADS_PREFER_PTHREAD_FLAG TRUE )