[cmake-developers] Missing Bullseye coverage on CMake Dashboard

Hi, I was curious about Bullseye coverage integration with CDash and thought to remember that this was available on CMake's Dashboard at some point. Currently I see a "Linux-bullseye-cov" build but no entry under "Coverage". Is that expected or did this break at some point? Nils -- Powered

Re: [cmake-developers] Enabling SSL support by default when building CMake from source

On Thu, Aug 9, 2018 at 2:54 PM Craig Scott wrote: > When building CMake from source with default options, you typically end up > without SSL support, even if the necessary libraries (i.e. OpenSSL) are > available. I've been bitten by that in my earlier days building CMake and > I've seen others

Re: [cmake-developers] Race between ADD_CUSTOM_COMMAND()

On 04.07.2018 18:52, Oleh Kravchenko wrote: Hello CMake Developers! Looks like I found interesting bug in CMake: - ADD_CUSTOM_TARGET() always creates Makefile rule for ADD_CUSTOM_COMMAND(). - As result build simetimes failed if specified -jN for make. FWIW this is documented behavior (so not

Re: [cmake-developers] Using USES_TERMINAL in ExternalProject.cmake

On 13.07.2017 22:19, Robert Dailey wrote: I noticed that ExternalProject_Add() has this same issue when run from Ninja. I do not see real-time output of the progress. Would it work to set USES_TERMINAL for most (if not all) custom commands and targets in ExternalProject.cmake? See the

Re: [cmake-developers] [ANNOUNCE] CMake 3.8.0-rc1 now ready for testing!

On 02/07/2017 07:13 PM, Robert Maynard wrote: * The "execute_process()" command gained an "ENCODING" option to specify on Windows which encoding is used for output from child process. Introduction of the new ENCODING option changed the implicit default output encoding which breaks

Re: [cmake-developers] CMake server-mode aborting

On 01/26/2017 10:45 AM, Tobias Hunger wrote: Hello CMake developers, I have been using Qt Creator extensively with cmake server-mode for a while now and am very happy with the results so far. Once the project is initially configured by cmake it is really nice. Today I started to look into a

Re: [cmake-developers] Requesting Advice: Installing object files

On 17.01.2017 23:25, Chris Bieneman wrote: Hello CMake-developers! In one of the LLVM sub-projects we have a problem where we need to install object files, which doesn't seem like a particularly easy task. I'm curious if anyone has any advice on how to approach this problem. The patch is

Re: [cmake-developers] Is there a way in CMake to get a list of all CTest tests added with add_test?

On 04.10.2016 11:20, Tobias Hunger wrote: On Mo, 2016-10-03 at 14:25 -0400, Brad King wrote: The list we need would thus be built up to contain all COMMAND arguments to add_test that are also build targets in CMake. The list would also need to include targets mentioned in generator expressions

Re: [cmake-developers] CPack [WiX] Customizations of individual features/components

On 09/30/2016 08:43 AM, Roman Wüger wrote: Hello, I want to customize some with CPack generated *.wxs files. For example: directories.wxs is generated with only the TARGET_DIR. TARGETDIR (no underscore) is always the one and only root-directory element [1]. How can I add an additional

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 09/09/2016 10:54 AM, Stuermer, Michael SP/HZA-ZSEP wrote: The details you miss if you are not using the features ... thanks for the hint, here is corrected patch. Michael Thanks. I merged to "next" with small changes. Nils -- Powered by www.kitware.com Please keep messages on-topic

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 09/06/2016 01:26 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Here it is. The patch only seems to allow patching Features generated for components but not Features generated for component groups. Is that intentional or an oversight? I think we should allow patching for both. Nils --

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 09/06/2016 01:26 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Yes I tried, didn't work somehow. Never mind, the current approach works. It should have worked. I've added a new working test case to my suite: https://github.com/ngladitz/cmake-wix-testsuite/tree/master/feature_ref_in_product

Re: [cmake-developers] PATCH: Bugfix for WIX support

On 06.09.2016 17:19, Stuermer, Michael SP/HZA-ZSEP wrote: I checked everything on our project. Works as expected so far. I had to add our CSharp patch(es) on top, so this is not a pure WIX feature test, but I think it's good to go. Thanks I reformatted, squashed and merged to "next" for

Re: [cmake-developers] PATCH: Bugfix for WIX support

On 09/06/2016 03:45 PM, Nils Gladitz wrote: https://cmake.org/gitweb?p=stage/cmake.git;a=commit;h=fe20015b13d6ccf10d99ff9b3d8f68919164fcf8 Please verify that I haven't broken anything. I broke writing of WIX include files. Should be fixed now: https://cmake.org/gitweb?p=stage/cmake.git

Re: [cmake-developers] PATCH: add custom xmlns namespaces into generated .wxs sources

On 09/06/2016 03:29 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Hm, I don't see how I can add a namespace before my patch fragment. If I want to use some element from let's say UtilExtension, I need to add the xmlns:util="http://schemas.microsoft.com/wix/UtilExtension; attribute in some parent

Re: [cmake-developers] PATCH: Bugfix for WIX support

On 09/06/2016 01:29 PM, Stuermer, Michael SP/HZA-ZSEP wrote: The generated guid values where not set correctly everywhere. This could lead to WIX build errors when using the CPACK_WIX_SKIP_PROGRAM_FOLDER option. Thanks. I modified the patch to work without the global/public

Re: [cmake-developers] PATCH: add custom xmlns namespaces into generated .wxs sources

On 09/06/2016 01:32 PM, Stuermer, Michael SP/HZA-ZSEP wrote: best regards, Michael Can you elaborate your use case for the patch? I assume this if for custom patch fragments? In that context wouldn't it suffice to add the namespace declarations to the elements that need them (in the patch

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 08/16/2016 11:15 AM, Stuermer, Michael SP/HZA-ZSEP wrote: There is precedence in cmWIXFilesSourceWriter::EmitComponentFile() so I think such an interface change would be fine. Ok I'll do this. Should solve all issues and doubts hopefully. Great. Thanks. Adding FeatureRef to #PRODUCT

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 08/12/2016 11:50 AM, Stuermer, Michael SP/HZA-ZSEP wrote: Patch 5 seems to implement patching of FeatureRef rather than the original Feature elements. I am not sure if this is what you intended but this could be error prone given that there could in theory be any number (0-n) FeatureRef

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 07/20/2016 03:58 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Using the patchfile support I managed to implement the service installation issue I had, so the unnecessary features from the last patch are removed now. I tested all patches separately and hope they work now. looking forward for

Re: [cmake-developers] [Patch 4/5] Improved WIX support

On 07/20/2016 03:58 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Using the patchfile support I managed to implement the service installation issue I had, so the unnecessary features from the last patch are removed now. I tested all patches separately and hope they work now. looking forward for

Re: [cmake-developers] [Patch 3/5] Improved WIX support

On 08/02/2016 01:29 PM, Stuermer, Michael SP/HZA-ZSEP wrote: -Original Message- From: Nils Gladitz [mailto:nilsglad...@gmail.com] Sent: Tuesday, August 02, 2016 10:47 AM To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers Subject: Re: [cmake-developers] [Patch 3/5] Improved WIX support

Re: [cmake-developers] [Patch 3/5] Improved WIX support

On 07/20/2016 03:58 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Using the patchfile support I managed to implement the service installation issue I had, so the unnecessary features from the last patch are removed now. I tested all patches separately and hope they work now. looking forward for

Re: [cmake-developers] [Patch 2/5] Improved WIX support

On 21.07.2016 17:32, Brad King wrote: On 07/21/2016 10:45 AM, Nils Gladitz wrote: I amended the commit message and added the otherwise missing release note. Thanks. Currently the release note is: +* The CPack WIX generator now supports CPACK_COMPONENT__DISABLED. + This can be used

Re: [cmake-developers] [Patch 2/5] Improved WIX support

On 07/20/2016 03:58 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Using the patchfile support I managed to implement the service installation issue I had, so the unnecessary features from the last patch are removed now. I tested all patches separately and hope they work now. looking forward for

Re: [cmake-developers] [Patch 1/5] Improved WIX support

On 07/20/2016 03:58 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Using the patchfile support I managed to implement the service installation issue I had, so the unnecessary features from the last patch are removed now. I tested all patches separately and hope they work now. looking forward for

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

Re: [cmake-developers] PATHS guess in find_package ignored with NO_DEFAULT_PATH & CMAKE_FIND_ROOT_PATH_MODE_PACKAGE

On 07/01/2016 02:08 PM, Julien Schueller wrote: *De: *"Nils Gladitz" <nilsglad...@gmail.com> *À: *"Julien Schueller" <schuel...@phimeca.com>, "cmake-developers"

Re: [cmake-developers] PATHS guess in find_package ignored with NO_DEFAULT_PATH & CMAKE_FIND_ROOT_PATH_MODE_PACKAGE

On 07/01/2016 11:13 AM, Julien Schueller wrote: I'm using find_package in no-module mode with the PATHS option to provide a hard-coded guess to a path where a sublibrary 'hmat' was previously found, and with the NO_DEFAULT_PATH to not find it first in system directories. find_package (HMAT

Re: [cmake-developers] CMake 32 and 64 bit packages on Windows

On 06/21/2016 03:37 PM, Brad King wrote: Nils, the installers in question were produced from your WiX installer work (thanks again for that!). Is this something wrong with the 64-bit installer or simply a Windows/MSI subtlety/bug? I can't try this out here right now but looking at the

Re: [cmake-developers] How can we add Find****

On 06/21/2016 10:57 AM, Farbos a wrote: I was wondering how can we add new Find.cmake. For examples I don't see any FindTBB, FindJsonCpp ... and I think some of them are used a lot. So my question is, Who decide if we can add new Find*** ? See

Re: [cmake-developers] FindPkgConfig and IMPORTED_TARGET in 3.6.0

On 06/17/2016 03:36 PM, Ben Boeckel wrote: Nils, the IMPORTED_TARGET feature in pkg_check_modules is nice! Thanks for that. However, it is hidden behind the check that pkg_check_modules uses to see if it already ran: I have not been involved in that development. From what I can tell this is

Re: [cmake-developers] ninja/make compilation response file

On 04.04.2016 18:38, Nils Gladitz wrote: On 04.04.2016 17:59, Dmitry Ivanov wrote: PS. Can we do something about bloated cmake ninja generator ? in our case cmake generates 1.8 Mb Makefile and 84 Mb build.ninja, though ninja is still faster than make even in this case. Curious. Did you

Re: [cmake-developers] ninja/make compilation response file

On 04.04.2016 17:59, Dmitry Ivanov wrote: PS. Can we do something about bloated cmake ninja generator ? in our case cmake generates 1.8 Mb Makefile and 84 Mb build.ninja, though ninja is still faster than make even in this case. Curious. Did you count the accumulative size of all Makefile

Re: [cmake-developers] Parallel ctest issues on the MinGW-w64/MSYS2 platform

On 29.03.2016 23:34, Alan W. Irwin wrote: On 2016-03-29 22:46+0200 Nils Gladitz wrote: On 29.03.2016 21:39, Alan W. Irwin wrote: One of the PLplot developers, Arjen Markus, has just reported to me that ctest -j4 for PLplot hangs on his MinGW-w64/MSYS2 platform while ctest works fine

Re: [cmake-developers] Parallel ctest issues on the MinGW-w64/MSYS2 platform

On 29.03.2016 21:39, Alan W. Irwin wrote: One of the PLplot developers, Arjen Markus, has just reported to me that ctest -j4 for PLplot hangs on his MinGW-w64/MSYS2 platform while ctest works fine. This issue occurred for the mingw64/mingw-w64-x86_64-cmake 3.4.1-1 package version of ctest.exe,

Re: [cmake-developers] find_package with NO_MODULE while cross-compiling

On 15.03.2016 23:01, Julien Schueller wrote: Hi, When using find_package ( NO_MODULE) while cross-compiling, cmake may find an existing Config.cmake in the host root path if Config.cmake is not available in the target root path. For example let's say that I have Qt5 project in my host Linux

Re: [cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

On 15.03.2016 21:44, Taylor Braun-Jones wrote: On Tue, Mar 15, 2016 at 4:28 AM, Nils Gladitz <nilsglad...@gmail.com> wrote: https://cmake.org/Bug/view.php?id=15578 https://cmake.org/Bug/view.php?id=15931 It seems like one of those reports should be marked as a duplicate of the

Re: [cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

On 03/15/2016 08:27 AM, Petr Kmoch wrote: Hi Taylor, I am afraid this behaviour is by design, so that ALL_BUILD can be the first target in the generated solution and thus the Startup project by default. However (speaking to the wider list audience), I would really appreciate an option to

Re: [cmake-developers] set_test_properties ignoring multiple properties

On 08.03.2016 22:36, Kael Dai wrote: Hi, I have a test that outputs multiple lines and want to use set_tests_properties with the PASS_REGULAR_EXPRESSION property to check different lines in the output. I've tried doing set_tests_properties(test1 PROPERTIES PASS_REGULAR_EXPRESSION "value1"

Re: [cmake-developers] Appending to LINK_FLAGS property of a target doesn't seem to work correctly

On 03.03.2016 22:57, Dan Liew wrote: Hi, I noticed recently is you do something like this add_executable(foo a.cpp b.cpp) set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-fopenmp") set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-static") then the flags that end up being passed to

Re: [cmake-developers] FindBOOST 3.5 target

On 01.03.2016 18:09, Henry Schreiner wrote: On FindBoost.cmake (and maybe others), the new (in 3.5) targets populate the INTERFACE_INCLUDE_DIRECTORIES directory. Shouldn’t this be the INTERFACE_SYSTEM_INCLUDE_DIRECTORIES field? Since that way CMake can help keep Xcode and other IDE’s from

Re: [cmake-developers] Run program/command before test

On 17.02.2016 07:58, Roman Wüger wrote: Ok thanks Would it be an opinion to have a COMMAND parameter for the add_test function like execute_process where every COMMAND must return the exit code and this would be ored? add_test(MyTest COMMAND myserver --port 80

Re: [cmake-developers] Is there a way to disable soname versioning?

On 01.02.2016 00:09, Eric Wing wrote: This has been an ongoing nuisance for me, so I thought I would finally ask. Is there a way I can force soname versioning without modifying everybody's CMake build scripts? The main problem is Android. Using soname versioning on Android will basically cause

Re: [cmake-developers] Adding source files not built by targets to CMake project

On 11/20/2015 04:43 PM, Marcus D. Hanwell wrote: I would like to see these files listed in Qt Creator (or insert your IDE of choice here). Is there anyway to do this, knowing that these files are not going to be built for a target (or compiled in any way). Any trick I am missing to make this

[cmake-developers] Directory listing for "Older Releases" no longer available

Following https://cmake.org/files from the Download page [1] I get: Directory index no longer supported. Please visit the download page. Is this intentional? The directory listing for "Current development distribution" [2] still works. Nils [1]

[cmake-developers] ALIAS target scope regression

The commit c389f8bb07e900d805ca3163f47b06e3dbe4303b cmLocalGenerator: Port Find method away from GetGeneratorTarget seems to have broken the following reduced test case: cmake_minimum_required(VERSION 3.3) project(Foo CXX) file(WRITE sub/CMakeLists.txt [[ file(WRITE foo.cpp

Re: [cmake-developers] CMake 3.4.0-rc2 ctest hangs with 100% CPU

On 23.10.2015 16:52, Brad King wrote: Thanks. Fixed: CTest: Fix regression in handling of a RUN_SERIAL test that fails https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e61973e1 I've queued this for merge to 'release' for 3.4.0-rc3. -Brad Thanks! Nils -- Powered by www.kitware.com

[cmake-developers] CMake 3.4.0-rc2 cpack xz compressed debian packages broken

Given this test case: cmake_minimum_required(VERSION 3.3) project(Foo NONE) install(FILES CMakeLists.txt DESTINATION tmp) set(CPACK_DEBIAN_COMPRESSION_TYPE "xz") set(CPACK_PACKAGE_CONTACT "f...@bar.com") include(CPack) A debian package created with: cpack -G DEB Fails during

[cmake-developers] CMake 3.4.0-rc2 ctest hangs with 100% CPU

I switched from 3.2.1 to 3.4.0-rc2 on a Windows and a Linux dashboard client for a custom project. On the Linux client parallel testing now loops with 100% CPU somewhere in cmCTestMultiProcessHandler::StartNextTests and cmCTestMultiProcessHandler::CheckOutput. I don't have a proper stack

Re: [cmake-developers] CMake 3.4.0-rc2 ctest hangs with 100% CPU

On 10/23/2015 09:10 AM, Nils Gladitz wrote: I switched from 3.2.1 to 3.4.0-rc2 on a Windows and a Linux dashboard client for a custom project. On the Linux client parallel testing now loops with 100% CPU somewhere in cmCTestMultiProcessHandler::StartNextTests and cmCTestMultiProcessHandler

Re: [cmake-developers] cmake fails to identify C and CXX compiler when building universal

On 09/29/2015 04:38 AM, Ryan Schmidt wrote: Hello, I am a developer with the MacPorts package management system, and I want to report to you a bug in cmake 3.3.2 that affects OS X. I was going to file a bug report in your issue tracker, but the bright yellow box at the top of the "report

Re: [cmake-developers] [CMake] [BUG] add_custom_command(TARGET ...) can't see in scope target

On 04.08.2015 23:15, Dan Liew wrote: foolib is defined in this CMakeLists.txt: https://github.com/delcypher/cmake_add_custom_command_bug/blob/master/lib/CMakeLists.txt That is the (only) context in which you can extend the definition of the target with custom commands. Since when? As far as

Re: [cmake-developers] [CMake] [BUG] add_custom_command(TARGET ...) can't see in scope target

On 04.08.2015 22:46, Dan Liew wrote: The target name foolib is unknown in this context. This warning is for project developers. Use -Wno-dev to suppress it ``` This doesn't make sense the target **clearly exists and is in scope** because the ``simple_test`` executable links against it and

Re: [cmake-developers] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped

On 07/31/2015 03:09 PM, Brad King wrote: I think some browsers or other download tools may automatically gunzip files during download. I seem to get that with Chromium too. The HTTP response for cmake-3.3.0.tar.gz does contain: Content-Encoding: x-gzip Which I think does tell clients

Re: [cmake-developers] CMAKE_MAP_IMPORTED_CONFIG_* missing implementation?

On 07/30/2015 03:28 PM, Brad King wrote: On 07/30/2015 08:45 AM, Nils Gladitz wrote: Am I missing something obvious? It can only work for the configurations that CMake knows about. For single-config generators (Makefiles, Ninja) this is the value of CMAKE_BUILD_TYPE. For multi-config

[cmake-developers] CMAKE_MAP_IMPORTED_CONFIG_* missing implementation?

I tried using http://www.cmake.org/cmake/help/v3.3/variable/CMAKE_MAP_IMPORTED_CONFIG_CONFIG.html in the following example: cmake_minimum_required(VERSION 3.3) project(Foo CXX) set(CMAKE_MAP_IMPORTED_CONFIG_RELWITHDEBINFO Release) add_library(foo SHARED IMPORTED) get_property(VAR

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

On 07/23/2015 03:47 PM, Konstantin Podsvirov wrote: http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducing-the-universal-crt.aspx CMake uses the module InstallRequiredSystemLibraries to install dependencies. Who is in charge here on this module? Should this module to install Universal

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

On 23.07.2015 17:24, James Johnston wrote: That sounds horrible - asking a user to manually run Windows Update. But Windows Update packages don't have to be installed ONLY by way of visiting Windows Update manually. The support issue is certainly cumbersome given that users will be told that

Re: [cmake-developers] Compact dependency graph

On 06/15/2015 09:46 PM, Richard Ulrich wrote: So here is the patch with tests and passing the git hooks. Thank you for the update and sorry again for the inconvenience. - Your commit's subject line looks a bit too long; I'd move the issue number into the bulk of the message (It should nicely

Re: [cmake-developers] cmake --help-policy CMP0057 MAIN_DEPENDENCY

On 05/12/2015 07:23 AM, James Bigler wrote: OK, thanks. I still think that if there is a difference in behavior for Makefile generators between MAIN_DEPENDENCY and DEPENDENCY there is a bug in CMake. Perhaps there needs to be bug filed for that. Here's the documentation: In makefile terms

Re: [cmake-developers] cmake --help-policy CMP0057 MAIN_DEPENDENCY

On 29.04.2015 09:11, Nils Gladitz wrote: The policy will likely have to be removed or replaced. I reverted the MAIN_DEPENDENCY specific CMP0057 commits and replaced the policy with an unrelated one that is part of my if-IN_LIST topic to fill the gap. This leaves the original issues

Re: [cmake-developers] Is there a way to avoid LOCATION property with Qt5?

On 04/28/2015 09:30 AM, Alan W. Irwin wrote: OK. Thanks, for pointing that out. Could you make that more obvious in http://www.cmake.org/cmake/help/v3.2/policy/CMP0026.html, i.e. change the summary line from Disallow use of the LOCATION target property. == Disallow use of the LOCATION

Re: [cmake-developers] Generator Expressions in CPack (Module) variables

On 04/28/2015 10:57 AM, Gregor Jasny wrote: Unfortunately the CPACK_BUILD_CONFIG approach does only work for multi-config generators. As far as I understand CPACK_BUILD_CONFIG gets only set if the -C command line option was given to cpack. But this option is only added conditionally and omitted

Re: [cmake-developers] Is there a way to avoid LOCATION property with Qt5?

On 04/28/2015 09:30 AM, Alan W. Irwin wrote: I don't understand exactly what you mean by configuration LOCATION returns. From what you said that term means something different from LOCATION_CONFIG and in any case is not relevant to my use case of generating pkg-config *.pc files with our build

Re: [cmake-developers] Is there a way to avoid LOCATION property with Qt5?

On 04/28/2015 08:00 AM, Alan W. Irwin wrote: The Qt5 cmake documentation at http://doc.qt.io/qt-5/cmake-manual.html which Steve has referred me to before states you should use the LOCATION property of targets to determine the actual path to libraries. The PLplot build system requires those

Re: [cmake-developers] cmake --help-policy CMP0057 MAIN_DEPENDENCY

On 04/27/2015 11:48 PM, James Bigler wrote: The problem is the current detection only barfs (unless I missed something - please correct if I'm wrong). What we need is detection and adaptation. Rather than telling the user, DON'T DO THAT! we should be helping the user out by saying, I know you

Re: [cmake-developers] cmake --help-policy CMP0057 MAIN_DEPENDENCY

On 04/27/2015 03:31 PM, Brad King wrote: The policy was added to diagnose some previously-broken cases earlier. We technically never supported duplicate MAIN_DEPENDENCY specification but did not diagnose it. Instead it could produce bad builds in some cases IIRC. Nils, do you remember where

Re: [cmake-developers] [CMake] cmake 3.1.1 does not generate x64 profile for visual studio

On 04/24/2015 02:22 PM, David Cole via cmake-developers wrote: We really shouldn't have removed the explicit mention of the Win64 suffixed generator names in the list of generators in --help ouput... That was a mistake. We should put it back. As I understand it the generator suffixes aren't

Re: [cmake-developers] Generator Expressions in CPack (Module) variables

On 24.04.2015 20:55, Gregor Jasny wrote: Hello, would it be possible to add generator expression support to CPack so that I can use $CONFIG within CPACK_PACKAGE_FILE_NAME? I'm using the CPack module from within my CMakeLists.txt. I'm trying to generate unique file names per architecture and

Re: [cmake-developers] [CMake] Bug in CMake GUI 3.2.1?

On 04/13/2015 04:28 PM, Robert Dailey wrote: I am running on Windows 8.1. Screenshots attached. Those are options for cmake itself rather than for the compiler: http://www.cmake.org/cmake/help/v3.2/manual/cmake.1.html Nils -- Powered by www.kitware.com Please keep messages on-topic and

Re: [cmake-developers] CTest update broken with non-ASCII filenames

On 09.04.2015 20:39, Rolf Eike Beer wrote: Am Donnerstag, 9. April 2015, 10:30:35 schrieb Brad King: On 04/09/2015 10:28 AM, Nils Gladitz wrote: What was the original problem you were trying to fix? You pointed out test failures on nibble.ngladitz which I then tried to fix: https

Re: [cmake-developers] CTest update broken with non-ASCII filenames

On 04/09/2015 04:15 PM, Brad King wrote: On 04/09/2015 07:54 AM, Nils Gladitz wrote: With c771f9d945444f6cfe41195e26653f368aff7f42 CTest: To enforce the C locale use LC_ALL instead of LC_MESSAGES. I think you meant commit 6a661f06: CTest: To enforce the C locale use LC_ALL instead

[cmake-developers] CTest update broken with non-ASCII filenames

With c771f9d945444f6cfe41195e26653f368aff7f42 CTest: To enforce the C locale use LC_ALL instead of LC_MESSAGES. I broke svn updates for repositories which contain non-ASCII filenames. This is apparently due to me not only changing how messages are encoded but also how svn interprets filename

Re: [cmake-developers] Fortran support for Ninja generator

On 03/24/2015 10:08 AM, Steven Vancoillie wrote: Dear all, we have a large Fortran project which we build with cmake and I'm interested in making the ninja generator work with Fortran. I found a few short discussions of this on the mailing list, but since then nothing has happened. One mention

Re: [cmake-developers] Extracting target metadata, IDE integration

On 15.03.2015 16:42, Tobias Hunger wrote: Hi Peter, CMake does know all the headers or it could not decide which files need rebuilding. The build system that CMake generates knows the header dependencies and decides when which files need rebuilding. CMake itself doesn't know. How header

Re: [cmake-developers] Generating buildsystem metadata from CMake

On 03/11/2015 11:10 AM, Stephen Kelly wrote: I'm starting to gather requirements and make sure the feature is well designed to satisfy the needs we're already aware of, and fits with the features CMake currently has. Source file groups (as in defined by source_group()) and target folders (as

Re: [cmake-developers] [CMake] Wrong behavior with 3.2.0-rc2

On 03/06/2015 10:22 AM, Pere Mato Vila wrote: Using version 3.2.0-rc2 on the Mac OS X 10.10 with the make generator. The following example executes the custom to create A.txt and B.txt twice when building with make -jN - cmake_minimum_required(VERSION 2.8.8 FATAL_ERROR)

[cmake-developers] CTestCoverageCollectGCOV and ctest_submit(CDASH_UPLOAD)

Hi, I saw ctest_submit(CDASH_UPLOAD)signature and the CTestCoverageCollectGCOV module being added to CMake. I was wondering how these differ in functionality from the old ctest_coverage() and ctest_upload(FILES). Specifically I couldn't tell from the existing documentation what new use

Re: [cmake-developers] cmake install command expected performance?

On 02/23/2015 04:13 PM, Robert Goulet wrote: I’m running into an issue were using the CMake install command to copy a directory with over 5000+ files (slightly over 1GB of data) takes a lot more time than doing a simple copy. On an SSD drive it takes 0.2 seconds to copy, while it takes about 56+

Re: [cmake-developers] build on multiple cores

On 01/27/2015 04:52 PM, Deepak Garg wrote: I want to build my cmake code with multiple cores (64). For this I am trying to test the build on 4 cores by typing make -j 4 But still build is done by a single core. The time taken for build by make and make -j 4 is same. Can anyone guide me

Re: [cmake-developers] FindOpenMP and gfortran

On 11/18/2014 04:10 PM, Alin Marin Elena wrote: the original bug/feature was introduced by this https://www.cmake.org/Bug/view.php?id=14656history=1 @Brad: Could this be fixed in time for 3.1? Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] FindOpenMP and gfortran

On 11/20/2014 02:32 PM, Brad King wrote: On 11/18/2014 10:10 AM, Alin Marin Elena wrote: 2. the fortran test in FindOpenMP.cmake shall be provided in fixed form (add 6 empty spaces in front of the character of each line) Please use this approach in a topic based of origin/release. Thanks,

Re: [cmake-developers] [PATCH] New module FindLibDl

On 19.11.2014 20:23, Roger Leigh wrote: libdl (for dlopen, dlsym) is part of (or an extention to) the standard library/linker on many platforms. It doesn't currently have support in CMake, though there are a few independent implementations shown up by Google. Given that there are several

[cmake-developers] $BUILD_INTERFACE genex regression

cmTarget: Refactor ComputeLinkImplementation (24637979): http://www.cmake.org/gitweb?p=cmake.git;a=commit;h=24637979 Seems to have broken this reduced testcase: cmake_minimum_required(VERSION 3.0) set(LIBRARIES foobar.lib barfoo.lib ) add_executable(foo foo.cpp)

Re: [cmake-developers] Ninja RC cmcldeps regression

On 10/10/2014 01:10 PM, Nils Gladitz wrote: Ninja on windows invokes the resource compiler through cmcldeps. When passing ${CMAKE_BINARY_DIR} as an include directory CMake used to (3.0) add the absolute path to the command line; now -I. is being added instead. The relative path does not seem

Re: [cmake-developers] $BUILD_INTERFACE genex regression

On 10/10/2014 03:14 PM, Brad King wrote: I can work around this by wrapping the libraries with $BUILD_INTERFACE individually or by quoting the entire genex. This was the intended interface. I'm willing to regress this because: - It restores 2.8.12 behavior - The quoting is easy to do - It is

Re: [cmake-developers] Ninja RC cmcldeps regression

On 10/10/2014 04:11 PM, Brad King wrote: Thanks, fixed and test added: Ninja: Fix RC include directories regression http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=23c8eeb7 Thanks! Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] Severe regression caused by #14972 fixes

On 10/07/2014 04:09 PM, Bill Hoffman wrote: On 10/7/2014 8:47 AM, Brad King wrote: Please note that from thehttp://www.cmake.org/Bug/view.php?id=14972 fixes on, we can no longer compile ReactOS. Also, if you really care about ReactOS, you could run a nightly cmake dashboard. Or it is almost

Re: [cmake-developers] Severe regression caused by #14972 fixes

On 10/07/2014 04:56 PM, Adam Strzelecki wrote: (1) Are these .spec, .inf or .idl generated by some custom commands? (2) If yes, are these files specified as an output of these subcommand commands? If no, why? From what I remember from the IRC discussion ... They are regular (not generated)

Re: [cmake-developers] Any ideas for accessing the Dart source code?

On 10/08/2014 12:46 AM, Alan W. Irwin wrote: I thought it would be interesting to install my own local dart server to learn how to use CTest as a dart client. You probably want the newer Kitware maintained replacement CDash: http://www.cdash.org/ Additional instructions for a local

[cmake-developers] CMP0053 - Simplify variable reference and escape sequence evaluation - regression

CMP0053 warns/fails on $ENV{ProgramFiles(x86)}. Could () be added to the legal set of characters when within an $ENV{} expansion? Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various

Re: [cmake-developers] CMP0053 - Simplify variable reference and escape sequence evaluation - regression

On 10/06/2014 02:48 PM, Brad King wrote: On 10/06/2014 06:39 AM, Nils Gladitz wrote: CMP0053 warns/fails on $ENV{ProgramFiles(x86)}. Could () be added to the legal set of characters when within an $ENV{} expansion? We considered that case and decided to ask users to use a nested variable

Re: [cmake-developers] kwsys SystemTools::RelativePath()

On 04.10.2014 02:25, David Cole wrote: Is the result of RelativePath guaranteed to be a directory name, or is it possibly a file name? If the second operand is a path to a file the result is a path to a file. If the second operand is a path to a directory the result is a path to a

Re: [cmake-developers] kwsys SystemTools::RelativePath()

On 03.10.2014 21:13, Brad King wrote: On 09/30/2014 10:05 AM, Nils Gladitz wrote: When both operands are the same absolute path I get the empty string as a result. Should it be .? Perhaps. One would need to track down existing call sites to see where that might affect behavior. IIRC

[cmake-developers] kwsys SystemTools::RelativePath()

When both operands are the same absolute path I get the empty string as a result. Should it be .? Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community.

Re: [cmake-developers] [CMake] Windows rpath emulation

On 09/20/2014 11:53 PM, Nils Gladitz wrote: On 20.09.2014 23:31, Roland Schulz wrote: it would be nice if there were a way to emulate rpath under Windows. As far as I can see there are two possible approaches: - Generate a shell script which sets PATH - Generate a manifest for the application

Re: [cmake-developers] [CMake] Windows rpath emulation

On 09/23/2014 03:11 PM, David Cole wrote: What is the problem that this feature is trying to solve? Being able to run binaries with DLL dependencies within the build tree. Basically the same thing that the build time RPATH feature does on e.g. linux. If you are e.g. linking to Qt5 (shared)

Re: [cmake-developers] [CMake] Windows rpath emulation

On 23.09.2014 19:12, Roland Schulz wrote: Have you got a solution to the problem you mentioned in your first email: I suppose it might be slightly more complex given that the import library that is being linked to and the DLL that corresponds to the import library might not be in

Re: [cmake-developers] Extracting target metadata, IDE integration

On 09/20/2014 09:57 PM, Tobias Hunger wrote: Hello! Sorry for breaking the threading, I only joined this ML just now to comment on this thread:-) Thanks Stephen for pointing me here! I am not a regular cmake user (used to be a couple of years ago), but I im interested in this topic since I

  1   2   3   >