Re: [CMake] Syntax to document cmake files, functions and macros

> Am 31.01.2019 um 19:55 schrieb Marc Herbert : > > So is there a relatively simple way to run the same tooling on any regular, > non-module .cmake files > too and produce project-specific documentation? We are working on a larger CMake project and we use Sphinx. We use

Re: [CMake] Checking Variables in a tool-chain file

> Am 31.01.2019 um 21:10 schrieb Craig Scott : > > This is precisely the scenario that the CMAKE_TRY_COMPILE_PLATFORM_VARIABLES > variable is meant for. It allows a toolchain file to specify additional > variables that should be passed along to try_compile(). Works like a charm. Thanks a lot!

[Cmake-commits] CMake branch, master, updated. v3.13.3-1265-g9512a58

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 3f37c95..0a65114 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 13) -set(CMake_VERSION_PATCH 20190131) +set(CMake_VER

Re: [CMake] Checking Variables in a tool-chain file

That’s perfect! It looks like it was introduced in CMake 3.6, whereas LLVM targets a minimum of 3.4.3 right now, but I’ll make a note of it for the next CMake upgrade. Thanks! From: CMake on behalf of Craig Scott Date: Thursday, January 31, 2019 at 12:10 PM To: "tors...@robitzki.de" Cc:

Re: [CMake] Checking Variables in a tool-chain file

This is precisely the scenario that the CMAKE_TRY_COMPILE_PLATFORM_VARIABLES variable is meant for. It allows a toolchain file to specify additional variables that should be passed along to try_compile(). On

Re: [CMake] Checking Variables in a tool-chain file

We have a somewhat similar problem with LLVM's toolchain file for cross-compiling to Windows, and we solve it there by saving and restoring cache variables from the environment inside the toolchain file itself. See

Re: [CMake] Syntax to document cmake files, functions and macros

> > On 24 Dec 2018, at 03:32, Oleksii Vilchanskyi gmail.com> wrote: > > On 12/24/18 12:01 PM, Olivier Croquette wrote: >> I have quite a few .cmake files that I want to document. They define >> functions, macros, and variables, and I was wondering if there is any >> standard or tooling to help.

[cmake-developers] CDash frontend refresh

We've been working on a refresh of CDash's look and feel. Before rolling this out, we wanted to give you all a sneak peek so that you could let us know what you think. Our proposed changes are now live on http://testing.cdash.org, which shares a backend database with https://open.cdash.org. For

Re: [cmake-developers] CMake 3.13 - Generated moc files not added to VStudio solution

Thanks! Worked, glad to have a smaller fix. VT On Thu, Jan 31, 2019 at 9:10 AM Sebastian Holtermann wrote: > > Any luck? I can try helping ya trace it if you need it. > > > > I traced this down to some degree. > The problem arises from the handling of file path for GENERATED vs non > GENERATED

Re: [cmake-developers] CMake 3.13 - Generated moc files not added to VStudio solution

> Any luck? I can try helping ya trace it if you need it. > I traced this down to some degree. The problem arises from the handling of file path for GENERATED vs non GENERATED files. When the full path for a file is computed in cmSourceFile and the file doesn't exist (mocs_compilation.cpp

Re: [cmake-developers] CMake 3.13 - Generated moc files not added to VStudio solution

Any luck? I can try helping ya trace it if you need it. Hoping to get this solved before the weekend xd On Wed, Jan 30, 2019 at 7:32 AM Venedict Tchistopolskii wrote: > Gotcha, my project builds atm and it's fairly large, didn't know that it > broke anything else. > > Please let me know when

[Cmake-commits] CMake branch, master, updated. v3.13.3-1264-gd526327

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via d526327079e23748dd2a87acd4d9b4b1174725bf (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.3-1245-g24bee42

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 24bee427b5da710c5f9941f5cddb455df1a2ea82 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.3-1231-g591899b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 591899bc9643881610f665ac2e8787774a6b78b0 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.3-1221-g5107a84

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5107a84d46ad245221843adbef092118649e6dc7 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.3-1215-g8ea30a4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 8ea30a44d38057fed134532f6d3b6e8626a1ccff (commit) via

Re: [CMake] Checking Variables in a tool-chain file

Hi Sergei, > Am 31.01.2019 um 08:42 schrieb Sergei Nikulov : > > Just guessing maybe better use $ENV{ARM_GCC_TOOL_PATH} ? > https://cmake.org/cmake/help/latest/variable/ENV.html?highlight=env Well, but this would mean, I had to configure CMake not only with Cache variables: cmake