Re: [CMake] skip install of subdirectory

Hi Alan, Thanks a lot! Yeah I was thinking about something along those lines, but i was wondering if there is a solution that does not involve modifying the submodules. On Wed, Jul 20, 2016 at 12:09 PM, Alan W. Irwin wrote: > On 2016-07-20 11:02-0700 Tiago Macarios

Re: [CMake] Using clang-tidy with cmake 3.6.0

On 7/20/2016 4:02 PM, Robert Maynard wrote: I believe the correct form is: set_target_properties(example PROPERTIES CXX_CLANG_TIDY "${path_to_tidy} -some -args") No, that won't work. You want it to be a semi-colon separated list of arguments. Not space separated.

Re: [CMake] Using clang-tidy with cmake 3.6.0

I believe the correct form is: set_target_properties(example PROPERTIES CXX_CLANG_TIDY "${path_to_tidy} -some -args") On Wed, Jul 20, 2016 at 9:02 AM, Theodoros Theodoridis wrote: > Hello everyone, > > I am trying to use the new _CLANG_TIDY property but I can't figure >

Re: [CMake] skip install of subdirectory

On 2016-07-20 11:02-0700 Tiago Macarios wrote: Hi, I have a project which uses git submodules to manage it's dependencies. Right now we want to add a installer to it, problem we have is that some of the dependencies have their own "install" directives. Is there a way to ignore a project

Re: [CMake] Why is target installation done in 2 separate steps?

I believe you can install and assign multiple targets in different subdirectories to a single export: /foo/CMakeLists.txt: install(TARGETS foo EXPORT mylib-targets ...) /bar/CMakeLists.txt install(TARGETS bar EXPORT mylib-targets ...) /CMakeLists.txt install(EXPORT mylib-targets

[CMake] skip install of subdirectory

Hi, I have a project which uses git submodules to manage it's dependencies. Right now we want to add a installer to it, problem we have is that some of the dependencies have their own "install" directives. Is there a way to ignore a project install command? Long version case it is unclear: main

[CMake] Using clang-tidy with cmake 3.6.0

Hello everyone, I am trying to use the new _CLANG_TIDY property but I can't figure out the proper syntax. How can I specify the checks I want? I tried setting the checks in set_target_properties(target PROPERTIES CXX_CLANG_TIDY "checks to be performed") but cmake would complain with "wrong

[CMake] object-libraries and compile-dependencies to other target

Hi list, I'm using an object-library to generate a list of .o-files instead of archives which I use to link into several executable. Even though it is only an object-library it has compile-dependencies to other targets - this includes include-paths, compile-definitions and compile-features. I

[CMake] [CMAKE] Call macro in CMake as last step

Hi all, I'm trying to emulate a custom global target (like the CMake install target). The only that came through is by only writing commands in a global variable throughout the cmakelists and at the very end, the last line in the top cmakelists.txt does an include(final) to create the target

Re: [CMake] object-libraries and compile-dependencies to other target

Hi Patrick, Can you provide a simple example of what you are trying to do, and where it is failing? On Wed, Jul 20, 2016 at 8:29 AM, Patrick Boettcher wrote: > Hi list, > > I'm using an object-library to generate a list of .o-files instead of > archives which I use

[Cmake-commits] CMake branch, next, updated. v3.6.0-936-g41da930

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-452-g811bcf5

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

Re: [cmake-developers] Security Report for CMake

On 19 Jul 2016, at 21:29, Brad King wrote: > On 07/19/2016 01:46 PM, Cyril VALLICARI wrote: >> Here a Patch that correct the vulnerability > > Thanks, applied: > > NSIS: Quote uninstaller path when executing it in a shell >

Re: [cmake-developers] Improved WIX support

> -Original Message- > From: Nils Gladitz [mailto:nilsglad...@gmail.com] > Sent: Wednesday, July 20, 2016 12:03 PM > To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers > Subject: Re: [cmake-developers] Improved WIX support > > On 19.07.2016 17:43, Stuermer, Michael SP/HZA-ZSEP wrote: > >

Re: [cmake-developers] Improved WIX support

On 19.07.2016 17:43, Stuermer, Michael SP/HZA-ZSEP wrote: Hello there, in short: I fixed some minor issues with WIX toolset support and added the possibility to integrate service installation/uninstallation with generated msi packages. Please review and comment what is missing for

[Cmake-commits] CMake branch, next, updated. v3.6.0-925-gd2a5bf0

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

Re: [cmake-developers] [PATCH v3 6/7] Use Windows version of Directory::Load for MinGW too

On 07/06/2016 03:12 PM, Dāvis Mosāns wrote: > Otherwise it would use POSIX functions which works only for ASCII paths. Thanks. Applied to KWSys first with minor tweaks: http://review.source.kitware.com/21349 -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the

Re: [cmake-developers] [PATCH v4] For consoles output on Windows use our own std::streambuf

On 07/09/2016 10:12 PM, Dāvis Mosāns wrote: > int main(int ac, char const* const* av) > { > +#if defined(_WIN32) > + // Replace streambuf so we can output Unicode to console > + cmsys::ConsoleBuf *cbufio = CM_NULLPTR; > + cmsys::ConsoleBuf *cbuferr = CM_NULLPTR; > + std::streambuf *coutbuf =

Re: [cmake-developers] [PATCH v4 3/4] Use SystemTools::GetEnv and HasEnv functions

On 07/18/2016 10:00 AM, Brad King wrote: > On 07/07/2016 05:54 PM, Dāvis Mosāns wrote: >> Source/kwsys/SystemTools.cxx| 38 >> +++-- >> Source/kwsys/testSystemTools.cxx| 9 --- > > Applied to upstream KWSys first: > >

Re: [cmake-developers] [PATCH v4 2/4] Deprecate const char* SystemTools::GetEnv function

On 07/07/2016 05:54 PM, Dāvis Mosāns wrote: > Source/kwsys/SystemTools.hxx.in | 14 -- Thanks. Applied to KWSys first: http://review.source.kitware.com/21348 -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] [PATCH v5 2/2] Add MinGW support for FStream

On 07/18/2016 09:28 AM, Brad King wrote: > Thanks. I've added this and its parent commit to KWSys: > > http://review.source.kitware.com/21339 This is now in KWSys `master`. I've updated it in CMake: KWSys 2016-07-19 (9d1dbd95) https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9ef2b2b1

[Cmake-commits] CMake branch, next, updated. v3.6.0-917-gb761ed2

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-448-g6a98785

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-451-gdf14a98

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-921-gabaec38

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-923-gb0f86b5

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

Re: [cmake-developers] Security Report for CMake

On 07/20/2016 02:31 AM, Justin Clift wrote: > Amir pointed out there may be other locations with the same > unquoted path problem in the template. Thanks. I'm not very familiar with NSIS or the syntax in the template file so we'll be dependent on others to find/fix any remaining problems.

[Cmake-commits] CMake branch, next, updated. v3.6.0-913-gb5d5b87

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

[cmake-developers] patch VS2010 generator : handle VS_GLOBAL_RootNamespace as well as VS_GLOBAL_ROOTNAMESPACE

Hi folks, As user I'm currently working on migrating C++CLI projects to CMake. I wasted a few hours because I used VS_GLOBAL_RootNamespace (a specialized version of VS_GLOBAL_ property) instead of VS_GLOBAL_ROOTNAMESPACE. So here is a patch to save the next one from wasting those same hours.

[Cmake-commits] CMake branch, next, updated. v3.6.0-927-g91ec400

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-933-g927ab80

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-929-g5617062

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-931-g467a182

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