Re: [CMake] Disabling INSTALL target for subdirectory

You can use the COMPONENT option to install() for your own project and then select a component-based package if you are packaging with CPack. We currently do this with builds that incorporate other projects with add_subdirectory() similar to your case. If you are using install as a build target

[CMake] Disabling INSTALL target for subdirectory

Hi, we are using the CMake install mechanism "install(...)" to copy all relevant files and target binaries of the product into the CMake install prefix folder, for further packaging. So far so good. We are also using several thirdparty libraries, hosting them inside our own repository and

Re: [CMake] Disabling INSTALL target for subdirectory

Hello all!10:00, 16 February 2017 г., Milan Ziegler :Hi,we are using the CMake install mechanism "install(...)" to copy allrelevant files and target binaries of the product into the CMake installprefix folder, for further packaging. So far so good.We are also using several

[CMake] Intel C Generator for Cmake?

I am having to switch to cmake from autotools for a third party tool I want to build. We use Intel C and Intel Fortran on Windows. I see no mention of an Intel C generator for cmake. I presume this means there is not one? If so, can I create my own Intel C generator please? Rgeards, Tony -- *Dr

Re: [CMake] Intel C Generator for Cmake?

Thank you so much Petr. I am new to cmake so did quite understand how everything fits together. I will give your suggestion a try. Regards, Tony On Wed, Feb 15, 2017 at 12:25 PM, Petr Kmoch wrote: > Hi Tony, > > generators are for different *buildsystems*: a generator

Re: [CMake] Intel C Generator for Cmake?

Hi Tony, generators are for different *buildsystems*: a generator for Makefiles, a generator for Visual Studio solutions, a generator for Ninja files, a generator for Eclipse projects etc. Intel C and Intel Fortran are compilers, not buildsystems. You should be able to use them with any

Re: [CMake] Potential bug: Having executables named "test" causes Ninja generator to generate ambiguous rules...

On 14.02.2017 22:53, Malfettone, Kris wrote: If so, are executables named “test” no longer supported? Am I missing something or wrong in some way? Issues existed before 3.0 but since 3.0 "test" and similarly problematic target names have been explicitly reserved. Any CMake Version >= 3.0

Re: [CMake] Intel C Generator for Cmake?

Re: my previous email. To use the Intel C compilers I just can modify the VS settings. So I have a way forward. Regards, Tony On Wed, Feb 15, 2017 at 12:25 PM, Petr Kmoch wrote: > Hi Tony, > > generators are for different *buildsystems*: a generator for Makefiles, a >

Re: [CMake] Potential bug: Having executables named "test" causes Ninja generator to generate ambiguous rules...

Good to know. Thanks for the quick response. Though I do not believe I am violating that particular rule here. That is why I do not receive either a warning or error from CMake in my output. The only warning I see is from ninja: ninja: warning: multiple rules generate

Re: [CMake] Intel C Generator for Cmake?

I tried setting the FC and CC variables and yet cmake still wants to use the Microsoft compiler (BTW what I am building is the CGNS - the CFD common file format). Is there something I am missing? CGNS_Build>set CC=icc CGNS_Build>set FC=ifort CGNS_Build>set CC CC=icc CGNS_Build>set FC FC=ifort

Re: [CMake] Potential bug: Having executables named "test" causes Ninja generator to generate ambiguous rules...

So I was able to reproduce the problem with this very simple CMakeLists.txt setup. I cannot attach source files due to my company's mail server automatically stripping them out attachments with code but here is all you would need to reproduce the problem: Single CMakeLists.txt with the

[CMake] import external library

Hi @all, I’ve tried importing an external library like that: stackoverflow.com/questions/31274577 I have the same use case, except that my custom target does not call make but does unpack a tar archive containing headers and .a. My problem is that the step “ # specify where the library is and

Re: [CMake] cmake 3.7.2 centos 7 :: kwsys.testSystemTools (Failed)

Hi Adrian, So, would this imply that cmake is not supported on EL7 because gcc does > not support cxx11 ? > That's not really what's happening. CMake is testing the C compiler to determine whether or not it supports C11 features and the C++ compiler to see if it supports C++11. The error

Re: [CMake] set_if_not_set

15.02.2017, 20:08, "Bill Newcomb" : > My top-level CMakeLists.txt files always end up with a lot of > > if(NOT_DEFINED foo) >  set(foo bar) > endif() > > things to allow people to pass interesting things on the command line or > to write their own "set this and that"

Re: [CMake] Problem with override file ...

I found that changing the add_definitions lines to set(CMAKE_C_FLAGS_INIT ...) or set(CMAKE_CXX_FLAGS_INIT ...) resolved the issue. I have not found documentation anywhere that says "this is how it must be done". So, is this the expected behavior when using

Re: [CMake] Intel C Generator for Cmake?

Toolchain is probably what you want http://stackoverflow.com/questions/9129233/recommended-ways-to-use-cmake-with-icc-via-configuration-options https://cmake.org/Wiki/CMake_FAQ#How_do_I_use_a_different_compiler.3F "cmake intel toochain" search. On Wed, Feb 15, 2017 at 6:42 AM, Thompson, KT

Re: [CMake] import external library

You can either unpack the target at generation time (recommended). Or you could create an INTERFACE target instead. The first solution is recommended as I believe it's important to have access to all the sources (for IDEs for example) before actually starting the build process. /Florent On

[CMake] set_if_not_set

My top-level CMakeLists.txt files always end up with a lot of if(NOT_DEFINED foo) set(foo bar) endif() things to allow people to pass interesting things on the command line or to write their own "set this and that" CMakeLists.txt and include the top-level one. It would improve

[CMake] Errors from CDash

When I run php5 autoRemoveBuilds.php all for my cdash 2.2.3 installation, I see the following errors (and old builds are not removed): removing builds for all -- removing old buildids for projectid: 2 PHP Warning: mysql_fetch_array() expects parameter 1 to be resource, boolean g8 PHP

Re: [CMake] Potential bug: Having executables named "test" causes Ninja generator to generate ambiguous rules...

On 15.02.2017 15:16, Malfettone, Kris wrote: Just noticed a problem in my example. In my attempt to simplify my example I moved both outputs into the same folder which in my opinion is invalid because both output file names are the same. However, the same basic setup does reproduce the

Re: [CMake] Potential bug: Having executables named "test" causes Ninja generator to generate ambiguous rules...

Just noticed a problem in my example. In my attempt to simplify my example I moved both outputs into the same folder which in my opinion is invalid because both output file names are the same. However, the same basic setup does reproduce the problem if you move the two targets into their own

Re: [CMake] Intel C Generator for Cmake?

Tony, I don’t have access to the Intel compiler on Windows to try this out. However, in an old post I found, it was suggested that you can use cmake’s “-T” option to select the Intel compiler when the generator is “Visual Studio”. For example: -T"Intel C++ Compiler XE 13.0" Ref:

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-103-gb922994

_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170215) +set(CMake_VERSION_PATCH 20170216) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-160-g258250c

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, next has been updated via 258250c4452bf6d73a0065d5914ce55360603d84 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-89-g8ba5c21

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 8ba5c21db774cb23d223612ba67963723010e9f3 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-94-g99ca1e2

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 99ca1e27e2453977d9b6e1b2a886c5b767fa9606 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-87-g75040fc

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 75040fc103b763092e54274d088659da792e72e8 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-96-g6a5e5a9

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 6a5e5a926817f7318a2a80822aa2ce28674344f4 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-99-g8ff8766

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 8ff87662325b2f2c21600da03fb78bca142c (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-92-ge853dfe

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 e853dfed6aef2dccc6bf05b6d19a5911e76f51c6 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-175-g13314a3

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, next has been updated via 13314a3e27942a44e747a9ba52e0c819a1b602d2 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-157-gc497701

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, next has been updated via c4977015291e195193f0e529d86ebc039e009907 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc1-18-g272c348

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, release has been updated via 272c348d5a1c3f713586e05e0d73fd18441f7bb2 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-172-g4e93e90

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, next has been updated via 4e93e9036ad904278b1634e082dbc627aea868e8 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-102-g72cfb3c

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 72cfb3c3d2e8f6167cf08289691f7b0c61d0d331 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-182-gb0ea076

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, next has been updated via b0ea076370600cd3e6a5d04a90667c0d2a8e4727 (commit) via

Re: [cmake-developers] Debugger for CMake

On 02/13/2017 10:18 PM, Justin Berger wrote: > Should I resumbit the MR to continue the discussion there? Justin submitted a new MR [1]. I encourage everyone that participated in this thread to take a look. Thanks, -Brad [1] https://gitlab.kitware.com/cmake/cmake/merge_requests/483 --

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-188-g2556769

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, next has been updated via 2556769b73a707529a73df5a474620281e3fb7d8 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-190-g37537d9

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, next has been updated via 37537d95cbcb3e7265599523bd31fe13cef25654 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-192-ge080ad3

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, next has been updated via e080ad36397d6b7d813b3b1c26a78414858c668a (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-179-gd4c222c

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, next has been updated via d4c222c5af0612ae0ec200bc540a733d0941fa19 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-184-gdd0648f

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, next has been updated via dd0648f5baa4a6ddf640191fb9c82fc300c3732b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-177-ga146979

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, next has been updated via a146979be3b0890d376f6c722f3b0744189367c9 (commit) via