Re: [CMake] "Pre-configure" step in CMake

Hi Matthaus, do you need the pre-configure step to happen at build time? Would it be an option for you to use file(WRITE) instead of configure_file(), and execute_process() instead of add_custom_target()? Basically, perform the pre-configure step as part of the first CMake run itself.

[CMake] Build log generation in a "custom" way

Dear All, I'd like to ask for some advice about the following issue. We're migrating a very big project (millions of lines of code...) from a custom build manager to CMake. The software is put together from separate "packages" that are all developed by a different set of people. Our nightly

Re: [CMake] Generated .rc files silently ignored

Hej hej, for some reason your mail was not delivered to me and I only stumbled upon it by chance in the archives (while trying to find out where another one of my mails to the list disappeared to). In any case, yes, I am adding the .rc file to my add_library command. The issue I have is that

[cmake-developers] Patch: install universal iOS libraries

Hi, Patches help to install universal iOS (device + simulator) libraries by triggering some extra instructions (build + fuse) after "regular" library installation finished. This behavior controlled by CMake variable CMAKE_IOS_INSTALL_UNIVERSAL_LIBS. = Example = > cat CMakeLists.txt

Re: [CMake] "Pre-configure" step in CMake

What if you call your dependency-fetcher script with a straight macro/function call or `include` or `execute_process` instead of putting it into a custom target? I'm thinking of something like this: set(DEP_SCRIPT_OUT ${CMAKE_CURRENT_BINARY_DIR}/dep-script-out.cmake) if(NOT EXISTS

Re: [cmake-developers] Help with diagnosing dashboard failure

Brad King wrote: > On 09/23/2015 03:13 PM, Stephen Kelly wrote: >> The end result of the current fix-max-path-initialization branch is the >> same as it was then. > > Okay. I can reproduce it with the current topic (ba7f7067..16354083). > Within the topic it bisects to: > >

Re: [cmake-developers] [CPack][BUG] Fail to package with CPACK_INSTALLED_DIRECTORIES

2015-09-23 17:00 GMT+02:00 CHEVRIER, Marc : > Any comments about this problem? Sorry I've forgotten about this mail... From what you're describing it should work. I'll take a look later today and get back to you then. Thanks, Domen -- Powered by www.kitware.com Please

Re: [cmake-developers] generator expression for path slash conversion

Unfortunately, "pushd" is an inappropriate command to use when the argument is quoted. It works just fine with "/" characters if the argument is quoted... For example: C:\Users\davidcole>pushd C:\Windows\System32 C:\Windows\System32>pushd C:/dev The syntax of the command is

Re: [cmake-developers] generator expression for path slash conversion

I factored out the code from cmOutputConverter::ConvertToOutputFormat() into another helper method called ConvertDirectorySeparatorsForShell(), changed the SHELL_PATH genex to accept only absolute paths, and changed its documentation accordingly. I also added a BadSHELL_PATH test to the

[Cmake-commits] CMake branch, next, updated. v3.3.2-3235-gd6b6e47

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

[Cmake-commits] CMake branch, next, updated. v3.3.2-3241-gcad1b3e

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

Re: [cmake-developers] Add command line options for deprecation message control

On 09/22/2015 08:53 AM, Brad King wrote: > In this case we have a bug in a new feature that was > introduced in post-3.3 development so we need to either fix it or > remove the offending parts of the new features before Oct 1 for 3.4. In preparation for the 3.4 freeze I've added a topic to revert

Re: [CMake] Build log generation in a "custom" way

On 9/24/2015 7:47 AM, Attila Krasznahorkay wrote: Dear All, I'd like to ask for some advice about the following issue. We're migrating a very big project (millions of lines of code...) from a custom build manager to CMake. The software is put together from separate "packages" that are all

[Cmake-commits] CMake branch, next, updated. v3.3.2-3238-ga0717a6

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

Re: [cmake-developers] generator expression for path slash conversion

Great, thank you, Brad & David. Regarding the ExternalProjectShellPathGenex test: I wrongly assumed that the WIN32 variable wouldn't be set when using MSYS and the like. Would it make sense to keep the test when changing the WIN32 check to MSVC? Good to know that pushd is working for quoted

Re: [cmake-developers] Generator expressions for install destination

On 09/23/2015 05:18 PM, Robert Goulet wrote: > Here is the patch to support genex for install(DIRECTORY) command > DESTINATION option. Thanks. Applied with minor tweaks: install: Allow generator expressions in DIRECTORY DESTINATION http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bd189cc2

Re: [cmake-developers] generator expression for path slash conversion

On 09/24/2015 09:05 AM, Kislinskiy, Stefan wrote: > I factored out the code from cmOutputConverter::ConvertToOutputFormat() > into another helper method called ConvertDirectorySeparatorsForShell(), > changed the SHELL_PATH genex to accept only absolute paths, and changed > its documentation

[CMake] CPack picks up AppleDouble files when running in OS X

Hi all, I've run into an annoying issue making package sources with CPack in OS X (Mavericks and Yosemite). I set up CPack to produce a tarball of my source tree with bzip, but in OS X tar will pick up the AppleDouble files in the source folder and stuff them into the archive too. As a result my

[Cmake-commits] CMake branch, master, updated. v3.3.2-1272-gcbfae8c

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

[Cmake-commits] CMake branch, next, updated. v3.3.2-3244-ge165b12

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

Re: [cmake-developers] generator expression for path slash conversion

> -Original Message- > From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] > On Behalf Of Kislinskiy, Stefan > Sent: Thursday, September 24, 2015 15:09 > To: Brad King > Cc: cmake-developers@cmake.org > Subject: Re: [cmake-developers] generator expression for path slash >

[Cmake-commits] CMake branch, next, updated. v3.3.2-3246-g527deef

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

Re: [CMake] "Pre-configure" step in CMake

On 9/24/2015 4:26 PM, Matthäus G. Chajdas wrote: Hi, that sounds like it would do the trick. I wasn't aware that execute_process will block the script until it's done executing. Need to check this out but that definitely looks like the way to go, thanks! ExternalProject might be a better

Re: [cmake-developers] [Patch] Adding Windows 10 support

On 09/23/2015 06:48 PM, Gilles Khouzam wrote: > This adds only the WINDOWS_TARGET_PLATFORM_VERSION property as it > currently only supports the desktop scenario and is extracted > from the rest of the Windows 10 Store support. Thanks. While reviewing this much simpler patch I realized that the

[CMake] Adding files to ARCHIVE packages only in CPack

How is it possible to add some files only to the ARCHIVE generators with CMake/CPack? Apparently components do that, but I can't figure how to say "only add component X to generator Y". I did something like this: In CPackConfig.cmake: set(CPACK_PROJECT_CONFIG_FILE

Re: [CMake] "Pre-configure" step in CMake

On 9/24/2015 5:02 PM, Matthäus G. Chajdas wrote: Hi, how does the ExternalProject interact with subsequent find_library calls? I've seen projects building dependencies through ExternalProject, but those would the project manually by querying ExternalProject and adding a new imported target.

Re: [cmake-developers] Generator expressions for install destination

Thanks Brad! Sent from mobile, please excuse typos. > On Sep 24, 2015, at 10:24 AM, Brad King wrote: > >> On 09/23/2015 05:18 PM, Robert Goulet wrote: >> Here is the patch to support genex for install(DIRECTORY) command >> DESTINATION option. > > Thanks. Applied with

Re: [cmake-developers] Add command line options for deprecation message control

I've created a fix for the issue of -Wno-dev and -Wno-deprecated options not being honoured, and extended the tests to cover this additional scenario. However I'm having an issue with determining if variables are set in cmake.cxx. The initial fix checked for the variables using the

[Cmake-commits] CMake branch, master, updated. v3.3.2-1273-g7c0b22a

_VERSION_MINOR 3) -set(CMake_VERSION_PATCH 20150924) +set(CMake_VERSION_PATCH 20150925) #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.3.2-3251-g0fe79c0

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

Re: [CMake] "Pre-configure" step in CMake

Hi, that sounds like it would do the trick. I wasn't aware that execute_process will block the script until it's done executing. Need to check this out but that definitely looks like the way to go, thanks! Cheers, Matthäus Am 24.09.2015 um 10:14 schrieb Tamás Kenéz: > What if you call your

Re: [CMake] "Pre-configure" step in CMake

Hi, how does the ExternalProject interact with subsequent find_library calls? I've seen projects building dependencies through ExternalProject, but those would the project manually by querying ExternalProject and adding a new imported target. How would I connect an ExternalProject to one or more