[CMake] [ANNOUNCE] CMake 3.11.0-rc4 is now ready for testing

I am proud to announce the fourth CMake 3.11 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.11 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.11/release/3.11.html Some of the more significa

Re: [CMake] Can't find Boost with Visual Studio 2017

On Sat, 2018-03-17 at 23:15 +0100, Volker Enderlein wrote: > Hi David, > > Boost changed its naming scheme starting from version 1.66. So its > not > your fault but the FindBoost.cmake does not know how to handle the > new > scheme. Try to use one of the 3.11.0-rc[1-3] versions that has the > p

Re: [CMake] Make ctest spit out xml file (without dashboard)

2018-03-19 13:14 GMT+01:00 Craig Scott : > > > On Mon, Mar 19, 2018 at 10:39 PM, Eric Noulard > wrote: > >> Hi there, >> >> Is it possible to make ctest spit out its result in an xml formatted file >> without >> sending it to some dashboard. ? >> > > Yes, you can control the individual steps of a

Re: [CMake] Generator Expressions and FetchContent

I do use target_link_libraries when it comes to C++ projects and it works wonderfully for them. However, in this case, my base project has a bunch of helper files with CMake functionality that help me work with and build my library of projects (which you can see here https://github.com/2LoC/tl_base

Re: [CMake] Make ctest spit out xml file (without dashboard)

On Mon, Mar 19, 2018 at 10:39 PM, Eric Noulard wrote: > Hi there, > > Is it possible to make ctest spit out its result in an xml formatted file > without > sending it to some dashboard. ? > Yes, you can control the individual steps of a full dashboard run and just leave out the submit step. For

Re: [CMake] Cmake Frameworks and Bitcode

On 03/12/2018 10:36 AM, Cameron Palmer wrote: > So after a bit of hacking it seems that Cmake should provide something like: > > CMAKE_OSX_BITCODE_ENABLE For reference, this refers to a previous post: Bitcode and CMake https://cmake.org/pipermail/cmake/2018-March/067191.html with the go

[CMake] Make ctest spit out xml file (without dashboard)

Hi there, Is it possible to make ctest spit out its result in an xml formatted file without sending it to some dashboard. ? I only need something xml-parsable ctest output locally. -- Eric -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cma

Re: [CMake] Generator for Visual Studio Code (Ubuntu)

You may also find this article useful, it seems to explain how to configure the JSON files you need to for more complicated build systems: https://medium.com/audelabs/c-development-using-visual-studio-code-cmake-and-lldb-d0f13d38c563

Re: [CMake] Generator Expressions and FetchContent

On Mon, Mar 19, 2018 at 8:25 AM, Saad Khattak wrote: > Thank you for the clarification Craig. > > >> If you made your main target link against LibA, you'd see that CMake > automatically expands out the generator expressions when it constructs the > link command line for main, so the example as it

Re: [CMake] Generator for Visual Studio Code (Ubuntu)

(you missed to reply to the mailing list!) On 19 March 2018 at 11:58, Richard Frank wrote: > Ok fair enough. So. I can output Unix make files and VS code can load those? Yes. If you have read the vscode-cmake extension docs https://vector-of-bool.github.io/, you would have seen that there is no

Re: [CMake] Generator for Visual Studio Code (Ubuntu)

On 19 March 2018 at 11:51, Richard Frank wrote: > Yes I have that plugin. But for more complex build systems that build > multiple products, running CMake from a shell script, I wondered what > generator would be used, FWIW, there no such thing as CMake generator for "Visual Studio Code". VSCode

Re: [CMake] Generator for Visual Studio Code (Ubuntu)

Yes I have that plugin. But for more complex build systems that build multiple products, running CMake from a shell script, I wondered what generator would be used, Sent from my iPad > On Mar 18, 2018, at 10:07 PM, Andrew Gaspar wrote: > > Hm, I’m not sure what you mean by built in support, b