[Cmake-commits] CMake branch, master, updated. v3.15.3-1190-gb42cb1f

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

[Cmake-commits] CMake branch, release, updated. v3.15.3-4-g5a35a9c

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

[Cmake-commits] CMake branch, master, updated. v3.15.3-1188-g76ae4c5

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

Re: [CMake] Single library with both shared and static binaries

On Tue, 2019-09-24 at 23:41 +0300, Avraham Shukron wrote: > Hi! > > I have a library which I want to distribute in both shared object and > static library forms. > Is there a modern way to do it without creating two completely > separate library targets? > Since I want to be a good CMake citizen

Re: [CMake] MacOS and shared libraries from imported targets

As far as I am aware, the macOS linker simply records the install name of the dynamic library you link against in your executable (similar to how the Linux linker records the Elf SONAME, if present). So, the first step would be to check the install name of the external dynamic library by

Re: [cmake-developers] Possible feature request concerning conditional linking support by generator expressions

On 2019-09-24 14:02-0700 Alan W. Irwin wrote: [...] I. Possible feature request After reading through the generator-expression documentation at it appears for my use case (see below) I need generator expressions of