[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-171-g5b64788c51

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 5b64788c51f7676276c0d8685003fd002b27388b (commit) from

Re: [cmake-developers] These two generator expressions should be equivalent, but one working while the other not working. Bug?

On 2019-10-24 12:41-0700 Alan W. Irwin wrote: [ W]ould you entertain a feature request to remove that hard-coded language limitation on the above 4 classes of genex so both internally and externally supported languages would work for all of them? Well, since you did not respond I assume

Re: [cmake-developers] generator expression in install RENAME

Please open an issue at https://gitlab.kitware.com/cmake/cmake/issues to request support for this. Kyle On Tue, Oct 29, 2019 at 9:58 AM Nicolas Desprès wrote: > > Hi there, > > Generator expressions are allowed in the FILES/PROGRAMS and DESTINATION part > of an install command. > > Would that

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc2-25-g449a29296d

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-170-g1fb4839225

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-157-gc5e22dfaea

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-155-ge90f6bacd5

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-153-g36516f0a50

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

[cmake-developers] generator expression in install RENAME

Hi there, Generator expressions are allowed in the FILES/PROGRAMS and DESTINATION part of an install command. Would that be possible to enable generator expression in the RENAME part as well? The use-case is for the TARGET_FILE_BASE_NAME expression. Cheers, -- Nicolas Desprès -- Powered by

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-148-gcffff0f17e

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 c0f17ef14fae6652ea5fd8c3511123a8e7b7 (commit) from

[cmake-developers] productbuild: Installing to absolute system path or to user home path

 Hello, I tried to install a file/directory with productbuild on macOS which is generated with CPack. The most of the files are installed correctly, but I have two problems: If I want to install to “/Library/Application\ Support/Adobe/Lightroom/Modules” If I want to install to the users

[CMake] productbuild: Installing to absolute system path or to user home path

 Hello, I tried to install a file/directory with productbuild on macOS which is generated with CPack. The most of the files are installed correctly, but I have two problems: If I want to install to “/Library/Application\ Support/Adobe/Lightroom/Modules” If I want to install to the users

Re: [CMake] How to Switch to Static Runtime on Command Line?

Hello, It has been a while since I've looked at this stuff, but I do use exceptions in my project. So I add the /EHsc: SET (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /fp:strict /EHsc ${WARNINGS_IGNORE}") SET (CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /fp:strict ${WARNINGS_IGNORE}") and I also add a linker

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-147-g92eb3a4475

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc2-16-g62267715fe

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-145-g336a826f77

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

Re: [CMake] How to Switch to Static Runtime on Command Line?

By default, CMake will use /EHsc when compiling for the Windows platform, with no option to change this that I am aware of. If a project wants different settings, it needs to handle this itself. And in fact, LLVM 3.4.2 conditionally modifies /EHsc to /EHs-c- in

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-140-gcb13aa580d

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

Re: [CMake] How to Switch to Static Runtime on Command Line?

On Mon, 28 Oct 2019 at 13:23, Eric Doenges wrote: > I think it is worth adding to what Mateusz wrote that the > MSVC_RUNTIME_LIBRARY property / CMAKE_MSVC_RUNTIME_LIBRARY variable are > only available if policy CMP0091 is set to NEW > Yes, indeed. FWIW, it is also documented in the frame "Note"

Re: [CMake] How to Switch to Static Runtime on Command Line?

On Mon, 28 Oct 2019 at 13:09, Osman Zakir wrote: > > I did read that. > I tried to specify CMAKE_MSVC_RUNTIME_LIBRARY and MSVC_RUNTIME_LIBRARY as > /MT, -MT and MT, but nothing worked. I'm sorry, but that confirms you did not read that document. Hint 1: "The allowed values are" Hint 2: In

Re: [CMake] How to Switch to Static Runtime on Command Line?

I think it is worth adding to what Mateusz wrote that the MSVC_RUNTIME_LIBRARY property / CMAKE_MSVC_RUNTIME_LIBRARY variable are only available if policy CMP0091 is set to NEW, which it will not be because LLVM's CMakeLists.txt only requires CMake 3.4.3 or later (and thus all policies

Re: [CMake] How to Switch to Static Runtime on Command Line?

Okay, actually I can't enable a static runtime for LLVM on the command line. I was told about a patch I need to apply. -- 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

Re: [CMake] How to Switch to Static Runtime on Command Line?

On Mon, 28 Oct 2019 at 12:22, Osman Zakir wrote: > > And I should do "-DCMAKE_MSVC_RUNTIME_LIBRARY=/MT" Man, read the docs I pasted!!! https://cmake.org/cmake/help/v3.15/prop_tgt/MSVC_RUNTIME_LIBRARY.html Best regards, -- Mateusz Loskot, http://mateusz.loskot.net -- Powered by

Re: [CMake] How to Switch to Static Runtime on Command Line?

I tried "-DCMAKE_MSVC_RUNTIME_LIBRARY=MT" and also "-DCMAKE_MSVC_RUNTIME_LIBRARY=/MT" before that, along with "-DCMAKE_BUILD_TYPE=Release", but I still get "Using Release VC++ CRT: MD". What's going on? I also did "-DCMAKE_CXX_FLAGS="/permissive- /EHsc /std:c++17 /O2 /MT

Re: [CMake] How to Switch to Static Runtime on Command Line?

Thanks for the reply. What about enabling C++ exceptions? And I should do "-DCMAKE_MSVC_RUNTIME_LIBRARY=/MT" to set the runtime type to static, right? -- 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

Re: [CMake] How to Switch to Static Runtime on Command Line?

On Mon, 28 Oct 2019 at 12:01, Osman Zakir wrote: > > I'm trying to build LLVM 10.0.0 with CMake on the command line (Developer > Command Prompt for VS2019) > and I need to know how to switch to a static runtime. This may help (CMake 3.15 or later only):

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-138-g6ad91699bf

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc2-13-gc79e9d8c21

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

[CMake] How to Switch to Static Runtime on Command Line?

Hi. I'm trying to build LLVM 10.0.0 with CMake on the command line (Developer Command Prompt for VS2019) and I need to know how to switch to a static runtime. I've tried specifying LLVM's variable for this, but it didn't work. I still have a dynamic runtime. Along with that, I also need to

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-135-gcdcc173e23

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-132-ge03b677e70

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

Re: [CMake] Got Weird Error When Trying to Configure LLVM Version 10

MSBuild is complaining that the generated project file doesn't contain a 32 bit debug target - which is no surprise, because you told CMake to generate a project for a release build. You will probably need to tell msbuild.exe that you want to build a release build with the

[CMake] Include VTK Project and Link Targets

Hello, I am having some difficulty trying to add an external project, in this particular case the VTK (Visualization Toolkit) project, to my own project using the *ExternalProject_Add *command. My goal is to download the project from the git repository to a *third_party_folder* in my repo and

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-130-g0e4190ba9e

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 0e4190ba9eaa46fe009394d5c5022818ef669bd9 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-129-gf3968470ce

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 f3968470ce71dbef596698816423efbf5c8f62d7 (commit) from

Re: [cmake-developers] [ANNOUNCE] CMake 3.16.0-rc2 is ready for testing

Hello, On 20.10.19 19:25, Robert Maynard via cmake-developers wrote: I am proud to announce the second CMake 3.16 release candidate. https://cmake.org/download/ CMake 3.16.0-rc2 successfully builds and tests our two large mono-repos. I'm looking forward to the release! Thanks, Gregor --

[CMake] Got Weird Error When Trying to Configure LLVM Version 10

I want to build LLVM 10 so that I can see if having the same version of LLVM installed that my EMSDK version is using will help. I want to do this so I can build the Qt Documentation as well when I build Qt for WebAssembly. Building the Documentation requires LLVM and I want to avoid

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-128-ga894397153

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 a8943971539aeb0df60b136d07e9c820c8be6f5e (commit) from

Re: [CMake] graphviz missing dependencies when target spans multiple subfolders

On Sat, Oct 26, 2019 at 9:11 AM Rich von Lehe wrote: > I am using CMake 3.15.1. Having found out about some of the changes with > 3.13, I've started to take advantage of using 'add_subdirectory()' in > certain cases when a module is large and spans multiple source folders. > > For instance: > >

Re: [CMake] Is there a "package" equivalent for CMAKE_SKIP_INSTALL_ALL_DEPENDENCY

On Sat, Oct 26, 2019 at 10:39 AM Scott Bloom wrote: > I’m looking for an equivalent to CMAKE_SKIP_INSTALL_ALL_DEPENDENCY for > packages, so when I do a make package, it doesn’t build all first. > > > > Does one exist? > You can just invoke cpack directly instead of doing a make package. --

[CMake] Is there a "package" equivalent for CMAKE_SKIP_INSTALL_ALL_DEPENDENCY

I'm looking for an equivalent to CMAKE_SKIP_INSTALL_ALL_DEPENDENCY for packages, so when I do a make package, it doesn't build all first. Does one exist? Scott -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

[CMake] configuring FCGI2 -- check typedefs in include files?

There are some things I'm trying to do in setting up a config file for the FCGI2 library: https://github.com/FastCGI-Archives/fcgi2.git And in going from an autoconf configuration to a CMake configuration there are some stumpers: /* Define if the fpos_t typedef is in stdio.h */ /*

[CMake] graphviz missing dependencies when target spans multiple subfolders

I am using CMake 3.15.1. Having found out about some of the changes with 3.13, I've started to take advantage of using 'add_subdirectory()' in certain cases when a module is large and spans multiple source folders. For instance: ModuleA/CMakeLists.txt:

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-127-g5c8d821eca

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

Re: [CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

Le jeu. 24 oct. 2019 à 22:32, Turner, Adrian Keith via CMake < cmake@cmake.org> a écrit : > Hi CMake Mailing List, > > > I am using the CHECK_CXX_COMPILER_FLAG directive in a CMake file to > detect whether the compiler uses the "-fsanitize=address" compiler flag. > I'm using the g++ 7.3.0

Re: [CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

This is the expected behaviour. As you already discovered, it is possible to control the compilation and link steps with variables as described in  https://cmake.org/cmake/help/latest/module/CheckCXXSourceCompiles.html#module:CheckCXXSourceCompiles. To specify, in a more clean way, link

Re: [CMake] Alternative locations for boost in cmake

>you have a "case discrepancy" between: >BOOST_INCLUDE_DIR >and>Boost_LIBRARY_DIRS Yes. Thank you Boost_LIBRARY_DIRandBoost_INCLUDE_DIR Are correct. The cmake is now fine. Regards, Mahmood -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] [DKIM: Failed] Re: Alternative locations for boost in cmake

Thank you. In addition to that, I have to write -DBoost_INCLUDE_DIR and not -DBOOST_INCLUDE_DIR It is not fine. Regards, Mahmood On Friday, October 25, 2019, 11:54:43 AM GMT+3:30, Marcel Loose wrote: Hi Mahmood, I think that "-DBoost_LIBRARY_DIRS" should be

Re: [CMake] Alternative locations for boost in cmake

On Fri, 25 Oct 2019 at 09:54, Mahmood Naderan wrote: > > Even with the latest 3.15.4, I get the same error > > Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem timer > chrono) (Required is at least version "1.58") You can try `-DBoost_DEBUG=ON that may give more clues what

Re: [CMake] [DKIM: Failed] Re: Alternative locations for boost in cmake

Hi Mahmood, I think that "-DBoost_LIBRARY_DIRS" should be "-DBoost_LIBRARY_DIR". Cheers, Marcel Loose. On 25/10/2019 09:54, Mahmood Naderan via CMake wrote: > Even with the latest 3.15.4, I get the same error > > > $ cmake --version > cmake version 3.15.4 > > CMake suite maintained and

Re: [CMake] Alternative locations for boost in cmake

Le ven. 25 oct. 2019 à 09:55, Mahmood Naderan via CMake a écrit : > Even with the latest 3.15.4, I get the same error > > > $ cmake --version > cmake version 3.15.4 > > CMake suite maintained and supported by Kitware (kitware.com/cmake). > $ cmake -DBoost_NO_SYSTEM_PATHS=ON >

Re: [CMake] Alternative locations for boost in cmake

Even with the latest 3.15.4, I get the same error $ cmake --version cmake version 3.15.4 CMake suite maintained and supported by Kitware (kitware.com/cmake). $ cmake -DBoost_NO_SYSTEM_PATHS=ON -DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-125-g5a3f539cd5

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 5a3f539cd50621298d15df639c29a9c09aace443 (commit) from

Re: [CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

I’ve dealt with that using something like this: set (_saved_CRL ${CMAKE_REQUIRED_LIBRARIES}) set (CMAKE_REQUIRED_LIBRARIES “-fsanitize=address;asan") check_cxx_compiler_flag (-fsanitize=address COMPILER_SUPPORTS_SAN) set (CMAKE_REQUIRED_LIBRARIES ${_saved_CRL}) the second item in

[CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

Hi CMake Mailing List, I am using the CHECK_CXX_COMPILER_FLAG directive in a CMake file to detect whether the compiler uses the "-fsanitize=address" compiler flag. I'm using the g++ 7.3.0 compiler which supports this flag but the CHECK_CXX_COMPILER_FLAG directive incorrectly determines that

Re: [CMake] VS2019 LLVM Toolset?

On Thu, 24 Oct 2019 at 21:36, Osman Zakir wrote: > > Yes, I looked at this: > https://devblogs.microsoft.com/cppblog/clang-llvm-support-in-visual-studio/ > so I kind of get it. VS2019 has built-in support for LLVM. I of course do > have LLVM installed. So for this, I have to put "ClangCL" as

Re: [cmake-developers] These two generator expressions should be equivalent, but one working while the other not working. Bug?

On 2019-10-24 08:08-0400 Brad King wrote: On 10/24/19 12:18 AM, Alan W. Irwin wrote: $ Expression did not evaluate to a known generator expression The `*_COMPILER_ID` generator expressions are a hard-coded set corresponding to the languages supported by upstream CMake: *

Re: [CMake] VS2019 LLVM Toolset?

Yes, I looked at this: https://devblogs.microsoft.com/cppblog/clang-llvm-support-in-visual-studio/ so I kind of get it. VS2019 has built-in support for LLVM. I of course do have LLVM installed. So for this, I have to put "ClangCL" as the argument to -T? Okay, thanks. I'll try that. --

Re: [CMake] Alternative locations for boost in cmake

On Thu, 24 Oct 2019 at 20:44, Mahmood Naderan wrote: > > Thank you. I tried this command: > > cmake -DBoost_NO_SYSTEM_PATHS=ON > -DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/ > -DBoost_LIBRARY_DIRS=/storage/users/mnaderan/boost_1_65_1/build/lib/ >

Re: [CMake] VS2019 LLVM Toolset?

On Thu, 24 Oct 2019 at 20:28, Osman Zakir wrote: > > Hi. I tried to specify the LLVM Toolset for VS2019 by doing "-T LLVM" and > also "-T llvm" but it failed both times. For me "-T ClangCL" seems to have worked (provided that you install Clang with VS 2019, of course). (To figure out the

Re: [CMake] Alternative locations for boost in cmake

Thank you. I tried this command: cmake -DBoost_NO_SYSTEM_PATHS=ON -DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/ -DBoost_LIBRARY_DIRS=/storage/users/mnaderan/boost_1_65_1/build/lib/ -DBoost_ADDITIONAL_VERSIONS=1.65.1 .. The paths are correct as you can see below: $ ls

[CMake] VS2019 LLVM Toolset?

Hi. I tried to specify the LLVM Toolset for VS2019 by doing "-T LLVM" and also "-T llvm" but it failed both times. What I get for the former is this: " cmake -G "Visual Studio 16 2019" -A x64 -T LLVM .. -DCMAKE_INSTALL_PREFIX="C:/Program Files/FLTK" -DCMAKE_BUILD_TYPE=Release CMake Error at

Re: [CMake] Alternative locations for boost in cmake

On Thu, 24 Oct 2019 at 19:05, Mahmood Naderan via CMake wrote: > > I have read https://cmake.org/cmake/help/v3.0/module/FindBoost.html which > states some variables for boost library. > I want to know where should I set these variables. For example, in the > terminal, I have written > > $

[CMake] Alternative locations for boost in cmake

Hi, I have read https://cmake.org/cmake/help/v3.0/module/FindBoost.html which states some variables for boost library. I want to know where should I set these variables. For example, in the terminal, I have written $ export Boost_NO_SYSTEM_PATHS=ON However, after I run "cmake ..", I see: --

Re: [CMake] Don't list Up-to-date files during install

Hi Jason, See the CMAKE_INSTALL_MESSAGE variable: https://cmake.org/cmake/help/v3.16/variable/CMAKE_INSTALL_MESSAGE.html setting this to “LAZY” should do what you want. Cheers, Ben. > On 24 Oct 2019, at 16:44, Jason

[CMake] Don't list Up-to-date files during install

When installing files, cmakes prints a list of all files that are to be installed, even if some of those files are already installed and up-to-date (i.e. installed from a previous build). If the file is not installed or out-of date, cmake prints "Installing: ..." and if a file was already

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-124-gb2b79e7776

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc2-8-g81ded33c04

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

Re: [cmake-developers] These two generator expressions should be equivalent, but one working while the other not working. Bug?

On 10/24/19 12:18 AM, Alan W. Irwin wrote: > $ > >Expression did not evaluate to a known generator expression The `*_COMPILER_ID` generator expressions are a hard-coded set corresponding to the languages supported by upstream CMake: * C_COMPILER_ID * CXX_COMPILER_ID * CUDA_COMPILER_ID

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-122-g11897b824c

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

[cmake-developers] These two generator expressions should be equivalent, but one working while the other not working. Bug?

Hi Brad: The two generator expressions $<$:-pthread> and $<$,$>:-pthread> are supposed to be equivalent according to the cmake-generator-expressions manual. Up to now I have always used the first form when setting the INTERFACE_LINK_OPTIONS property of an interface library which my D

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-116-g490da0bd33

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 490da0bd337f33c51884d7fe3bd5ac042ac0b0c5 (commit) from

Re: [CMake] Centos8 FindICU problems

On 23/10/2019 14:43, Kent Williams wrote: That works for me, but is this a documented thing anywhere? On 10/22/19 4:22 PM, Roger Leigh wrote: On 22/10/2019 21:51, Kent Williams wrote: find_package(ICU REQUIRED) It reports failure to find ICU, and I can't work out what I'm supposed to do:

Re: [CMake] Centos8 FindICU problems

That works for me, but is this a documented thing anywhere? On 10/22/19 4:22 PM, Roger Leigh wrote: On 22/10/2019 21:51, Kent Williams wrote: find_package(ICU REQUIRED) It reports failure to find ICU, and I can't work out what I'm supposed to do:     CMake Error at

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-115-g44b5f037e6

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 44b5f037e66e58cb4b5f9877b568bc40b9b576ca (commit) from

Re: [CMake] Centos8 FindICU problems

On 22/10/2019 21:51, Kent Williams wrote: find_package(ICU REQUIRED) It reports failure to find ICU, and I can't work out what I'm supposed to do:     CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):       Failed to find all ICU components

[CMake] Centos8 FindICU problems

This is a development system we're just standing up using Centos 8. Linux build8.leepfrog.com 4.18.0-80.7.1.el8_0.x86_64 #1 SMP Sat Aug 3 15:14:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux cmake version 3.11.4 gcc version 8.2.1 20180905 (Red Hat 8.2.1-3) (GCC) Installed Packages

Re: [CMake] Qt5 cmake imported target include path on MacOS

As an additional piece if information, if I run cmake with "-G Xcode" the command line contains: - -F/usr/local/opt/qt/lib - -F/Users//src//xcode/bin but if I run cmake with "-G Ninja" the command line contains: - -iframework /usr/local/opt/qt/lib On Tue, Oct 22, 2019 at 11:50 AM

[CMake] Fwd: Help needed with '-whole-archive,-export-dynamic'

Just to say, I have fixed this problem, so no help needed now. -- 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. For more information on each offering,

[CMake] Qt5 cmake imported target include path on MacOS

We are using the imported targets of Qt5 on macOS. When we do this the command line shows the include paths to the frameworks directory as "-F" where we would have expected "-iframework ". The former is leading the compiler to give us warnings when compiling the Qt provided header. Any ideas on

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-114-g04e0fa3307

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

[CMake] Help needed with '-whole-archive,-export-dynamic'

Hi I am porting a gnu make project to CMake. Initially I am using the Ninja generator and running in Ubuntu 18.04. The project consists of a static library 'libKernel.a', which includes main.cpp, which we link into an executable: 'MyApp'. The program dynamically loads shared libraries that need

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-112-g24703b11b4

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 24703b11b41e2e95d566ee911f0f87bdb47d4883 (commit) from

Re: [CMake] Policy Stack within Macros/Functions

On Mon, 2019-10-21 at 21:39 +0200, Sérgio Agostinho wrote: > For further users with the same problem, you likely do not need need > to invoke cmake_policy(PUSH)/cmake_policy(POP) from your shipped > Config file, so just delete them and set whatever policies you need > without concerns. This has

Re: [CMake] Policy Stack within Macros/Functions

Thank you for the tip. After rereading the documentation again, I noticed the following quote in the docs CMake also manages a new entry for scripts loaded by include() and find_package()

Re: [CMake] Custom installation of cmake

Thanks. I found it much easier to use the installer package (.sh file). I wanted a new gcc for building cmake. since the system default is 4.8.5. The installer package is available and installed that to my custom folder. Regards, Mahmood On Sunday, October 20, 2019, 8:58:25 PM GMT+3:30,

Re: [CMake] How to properly add include directories?

> > >What generator are you using? > Ninja > That thread seems to contain a lot of misunderstandings about the issue. > > If you are using the Makefile generator then refer to > https://stackoverflow.com/questions/7461000/handling-header-files-dependencies-with-cmake. > After building the

Re: [CMake] [EXT] How to properly add include directories?

Hello, Have you try to add the header files in the add_library command to explicitely add a dependency over it ? add_library(MyLib SHARED my_source.cpp ../MyHeaders/header.hpp etc.) On 10/21/19 4:16 PM, David Aldrich wrote: WARNING: External email, please be mindful before clicking or

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-111-g48459ab820

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

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc2-6-gfa1fe09dbb

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

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-96-g61c6d49f5a

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

Re: [CMake] How to properly add include directories?

On Mon, Oct 21, 2019, at 10:16 AM, David Aldrich wrote: > Hi again, > > My CMakeLists.txt file for my shared library contains: > > add_library(MyLib SHARED my_source.cpp etc.) > target_include_directories( MyLib PRIVATE ../MyHeaders) > > The library builds ok, but there is no dependency on

[CMake] How to properly add include directories?

Hi again, My CMakeLists.txt file for my shared library contains: add_library(MyLib SHARED my_source.cpp etc.) target_include_directories( MyLib PRIVATE ../MyHeaders) The library builds ok, but there is no dependency on directory ../MyHeaders - touching a header file does not result in a

Re: [CMake] Concerning ninja -v

> > >Does just invoking ninja with -v not show verbosity? That should do it. > > don't believe CMAKE_VERBOSE_MAKEFILE affects Ninja builds. > > >Kyle > Yes thanks, that does do it. I just wondered whether there was a neater way for when CMake is invoked by an IDE such as VS Code with the

Re: [CMake] Concerning ninja -v

On Mon, 2019-10-21 at 10:23 +0100, David Aldrich wrote: > I have a simple CMake project with subdirectories: > > cmake_minimum_required(VERSION 3.10) > project(MyProject VERSION 1.0.0) > > set(CMAKE_VERBOSE_MAKEFILE ON CACHE BOOL "ON") > > add_subdirectory(say-hello) >

Re: [CMake] Policy Stack within Macros/Functions

On Sun, 2019-10-20 at 19:25 +0200, Sérgio Agostinho wrote: > Hey everyone, > > I’m shipping a config file for my library and inside I set push/pop > specific policies so that me and the consumers of my library can > target different policies without us clashing against each other. > However I’m

Re: [cmake-developers] CTest load balancing

On 16/10/2019 15:10, Brad King wrote: > On 10/16/19 10:05 AM, Wouter Klouwen wrote: >> Is the intent for CTest to specifically manage CPU load or system load >> overall? > > I don't think a careful distinction was made at the time. > > If Linux needs some updates to be consistent with other

[CMake] Concerning ninja -v

I have a simple CMake project with subdirectories: cmake_minimum_required(VERSION 3.10) project(MyProject VERSION 1.0.0) set(CMAKE_VERBOSE_MAKEFILE ON CACHE BOOL "ON") add_subdirectory(say-hello) add_subdirectory(hello-exe) Will the 'CMAKE_VERBOSE_MAKEFILE' option be inherited by the

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-89-ga82a96f35b

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 a82a96f35b3970501cd552c36819f9313734f669 (commit) from

Re: [CMake] ExternalProject_Add Visual Studio build Install Target

On Sat, Aug 31, 2019 at 9:56 PM J Decker wrote: > Why does it seem I'm the only one with this problem? > This is an external CMakeLists.txt that fails. cmake_minimum_required(VERSION 3.15) set_property(GLOBAL PROPERTY USE_FOLDERS On) project( B ) include( ExternalProject )

<    1   2   3   4   5   6   7   8   9   10   >