[CMake] exclude a dependency from export

Is there any way to exclude a dependency from an export? If I build a static library target "A" but do not wish to install it, and then link that target to another target "B" using target_link_libraries(B A), and then attempt to export B, I get the error message: install (EXPORT "B" ...) includes

[CMake] Checking whether particular *linker* flags are supported

CMake has the macros CHECK_C_COMPILER_FLAG and CHECK_CXX_COMPILER_FLAG, which allow checking for whether a given C or C++ compiler flag is supported by the compiler being used. However, there's no CHECK_LINKER_FLAG macro, so that you can check whether a given *linker* flag is supported by the

Re: [CMake] PROPERTY for list of link libraries

I am now having a problem with transitive dependencies. I need all libraries that are linked in. I am missing the ones that are linked in transitively. Modified code is, ignoring J. Decker's suggestion about using generator expressions to get the path to the target's output. get_property(libs

Re: [CMake] exclude a dependency from export

Private doesn't work because the names in A need to be part of the public interface. On Fri, Jan 22, 2016 at 11:51 AM, Nicholas Braden < nicholas11bra...@gmail.com> wrote: > Have you tried using the PRIVATE keyword when linking to A? > >

Re: [CMake] exclude a dependency from export

I've found several workarounds, though I'm not sure of the long term ramifications. 1. I can "install" library A to CMAKE_CURRENT_BINARY_DIR effectively doing nothing. Since A is never referenced, only consumed, this should be okay? 2. I can remove the export from both A's and B's install, and

[CMake] Shared library for a executable

I have the need to have a shared library be created and then this same library be accessed by my executable. I want both to remain in different sibling directories and have one main CMakeList.txt that would call the other two CMakeList.txt (one in the lib dir, one in the exe dir) to build the

[CMake] Announcing Buildroot.cmake: a CMake module that wraps the Buildroot build system

Hello I'd like to announce the release of Buildroot.cmake, available here: This was developed thanks to Teufel, who make the Raumfeld multi-room audio system. The firmware for Raumfeld speakers is built using Buildroot. There are several

Re: [CMake] PROPERTY for list of link libraries

Ah yes, that was it. Switching to 3.3.2 did the trick. Time to upgrade cmake. On Fri, Jan 22, 2016 at 4:40 PM, Tom Kacvinsky wrote: > I am now having a problem with transitive dependencies. I need all > libraries that are linked in. I am missing the ones that

[CMake] string regexp replace removes the semicolons

Hi I want to remove from a list of sources those that start with 'foo' So I have file(GLOB ALL_SOURCES "*.cc") # this gives ALL_SOURCES = "a.cc;b.cc;foo_u.cc;foo_v.cc;c.cc;y.cc" # separated by semicolons string(REGEX REPLACE "foo.*cc" " " COMPILE_ONLY ${ALL_SOURCES}) But in the COMPILE_ONLY

[CMake] CTest integration in Visual Studio TestExplorer

Hello everyone, picking up the line from Tobias from around a year ago I changed a few things in the ctest unittest adapter. It now works for both Visual Studio 2013 and 2015. 2012 is supported in general but I didn't try it (means: I can install it). Merging and pull request for original

Re: [CMake] string regexp replace removes the semicolons

Hi, Command file(GLOB) returns a CMake list (in a CMake list, items are separated by ;) Now you pass to command string the content of the list, so the list is expanded: in your example, string(REGEX REPLACE "foo.*cc" " " COMPILE_ONLY ${ALL_SOURCES}) Is equivalent to: string(REGEX REPLACE

[Cmake-commits] CMake branch, master, updated. v3.4.2-895-gdcf977e

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-899-g1d9c539

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2088-ge9ac370

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2082-g54f9e33

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-897-gddb09ec

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-893-g666487a

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

Re: [CMake] Shared library for a executable

Hi Gonzalo, On Fri, Jan 22, 2016 at 1:49 AM, Gonzalo wrote: > I have the need to have a shared library be created and then this same > library be accessed by my executable. > I want both to remain in different sibling directories and have one main > CMakeList.txt that would

[CMake] PROPERTY for list of link libraries

I have need for a cross platform methods of getting libraries linked into an executable. Say for instance, we have add_library(foo STATIC a.c) add_exceutable(bar b.c) target_link_libraries(bar foo) So I know for that bar has a dependency on foo.lib (on Windows) and libfoo.a on Linux. And so

Re: [cmake-developers] Using CMake generated ninja file as a subninja file

On Fri, Jan 22, 2016 at 17:34:03 +0100, Nicolas Desprès wrote: > I have pushed a first draft of the patch here: > > https://github.com/nicolasdespres/CMake/commit/67a4faad47378c07c97a29dd229d6f9fa500763b > > I have tested with a small project and it looks good. Looks like a good start to me as

Re: [CMake] PROPERTY for list of link libraries

LOCATION was/is deprecated... the preferred method is generator expressions https://cmake.org/cmake/help/v3.3/manual/cmake-generator-expressions.7.html $ $ On Fri, Jan 22, 2016 at 7:19 AM, Tom Kacvinsky wrote: > On Fri, Jan 22, 2016 at 9:23 AM, Tom Kacvinsky >

Re: [CMake] PROPERTY for list of link libraries

Am 22. Januar 2016 15:23:53 MEZ, schrieb Tom Kacvinsky : >I have need for a cross platform methods of getting libraries linked >into an executable. > >Say for instance, we have > >add_library(foo STATIC a.c) >add_exceutable(bar b.c) >target_link_libraries(bar foo)

Re: [cmake-developers] Using CMake generated ninja file as a subninja file

Ben, I have pushed a first draft of the patch here: https://github.com/nicolasdespres/CMake/commit/67a4faad47378c07c97a29dd229d6f9fa500763b I have tested with a small project and it looks good. I would like to add some regression tests but I don't know from where to start. The principle would

[cmake-developers] [CMake 0015933]: The install command should have an option to only install built targets

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15933 == Reported By:Ilya Assigned To:

Re: [CMake] exclude a dependency from export

Have you tried using the PRIVATE keyword when linking to A? https://cmake.org/cmake/help/latest/command/target_link_libraries.html#libraries-for-a-target-and-or-its-dependents On Fri, Jan 22, 2016 at 9:14 AM, Jack Stalnaker wrote: > Is there any way to exclude a dependency

Re: [cmake-developers] CMake daemon for user tools

> -Original Message- > From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] > On Behalf Of Milian Wolff > Sent: Thursday, January 21, 2016 22:31 > To: Daniel Pfeifer > Cc: CMake Developers; Stephen Kelly > Subject: Re: [cmake-developers] CMake daemon for user tools > > >

[Cmake-commits] CMake branch, master, updated. v3.4.2-900-g4a3fa1e

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