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

2015-12-19 Thread Magnus Therning
Dave Flogeras writes: > 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`

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

2015-12-19 Thread Magnus Therning
Ruslan Baratov writes: > How about using RelWithDebInfo? See: > http://stackoverflow.com/a/28124715/2288008 Hmm, I'm probably missing something but how does that solve the issue with some targets requiring NDEBUG to be *undefined* and other targets requiring NDEBUG to be defined? /M > On 18-De

Re: [CMake] CMake, QT5 and cross compilation

2015-12-19 Thread Dave Flogeras
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 system,

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

2015-12-19 Thread Dave Flogeras
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 into > NOOPs. > > Is t

Re: [CMake] build order

2015-12-19 Thread Owen Hogarth II
Hi David Thank you for the response, I thought that I was doing something wrong. I mean it's documented and I followed the docs as close as possible to write my scripts but there's literally no mention about how to solve this external/ internal project setup in the official docs. I saw some thing

Re: [CMake] Feature request: expose curl to cmake -E

2015-12-19 Thread Greg Marr
iosif neitzke wrote: >On Fri, Dec 18, 2015 at 2:18 PM, Jakob van Bethlehem > wrote: >> Depending on what you precisely wish to achieve, maybe file(DOWNLOAD) >> already fits your needs? >> https://cmake.org/cmake/help/v3.1/command/file.html > >It does, generally, in the way that ExternalProject al

Re: [CMake] Feature request: expose curl to cmake -E

2015-12-19 Thread Jakob van Bethlehem
> > I thought 'curl' is sort of at the level of 'tar', in being a useful > tool that could be exposed fairly easily in a cmake portable command. Have you ever checked out the full man page of curl and the full feature list? (http://curl.haxx.se/docs/manpage.html) This is certainly not ‘easy’ to

Re: [CMake] Feature request: expose curl to cmake -E

2015-12-19 Thread iosif neitzke
Mostly yes. On Sat, Dec 19, 2015 at 8:45 AM, Greg Marr wrote: > iosif neitzke wrote: >>On Fri, Dec 18, 2015 at 2:18 PM, Jakob van Bethlehem >> wrote: >>> Depending on what you precisely wish to achieve, maybe file(DOWNLOAD) >>> already fits your needs? >>> https://cmake.org/cmake/help/v3.1/comm

Re: [CMake] build order

2015-12-19 Thread David Cole via CMake
Build the second thing as an ExternalProject, too, and use the DEPENDS keyword to make it build after the first thing. Don't try to mix-and-match external projects and non-external projects in the same CMake configure... It's just too much work to get things working in a reasonable cross-platfo