This patch adds the FindLTTngUST module which can be used to find
the LTTng-UST library. It sets result variables and creates an
imported target, LTTng::UST.
Since the module is able to find the LTTng-UST version string, this
is tested in Tests/CMakeOnly/AllFindModules.
The module is tested
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15994
==
Reported By:Steven Newbury
Assigned To:
On 02/28/2016 11:39 AM, Gregor Jasny via cmake-developers wrote:
> Brad: I pushed and merged the xcode-regenerate-on-deleted-files topic
> but I'm unsure about the test location itself and if this is a feature
> all generators should provide. I tested it with Xcode, Make, and Ninja.
Grep for
On 02/26/2016 08:18 PM, Philippe Proulx wrote:
> I submitted a v2, but I'm still wondering: do I need to extract the
> documentation somehow, to put it in Help/module, or is it
> automatically extracted once it's merged?
You need to add a Help/module/FindLTTngUST.rst file containing:
..
On 02/29/2016 06:59 AM, Eric Wing wrote:
> I see in the CMakeSwiftInformation.cmake, there is a
> . However, I do not see a ,
> just .
That is implicitly the flags for the corresponding language
since it appears in the compilation rule specific to the language.
> Additionally, in regular CMake
On 02/27/2016 09:38 AM, Mariusz Pluciński wrote:
> select appropriate toolset - "c140_clang_3_7". CMake already has support of
> toolsets, so it's already possible to generate VS project with the following
> command:
Gilles, IIRC you have been working on support for this too. Please take
a
As soon as this is merged in 'master' I will give it a try. We are extremely
interested to have C# support in CMake. That is the last piece of our entire
toolchain that is currently not using CMake, so it would be more than welcome
to have the entire system built with CMake.
Good job!
I'm finding that I'm going to need to completely separate the C FLAGS
from the Swift FLAGS. I hit some complicated situations where the C
FLAGS (both compile and linker) are confusing the process and
shouldn't be passed to Swift.
I see in the CMakeSwiftInformation.cmake, there is a
. However, I
