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

2019-09-26 Thread Simon Richter
Hi, On Tue, Sep 24, 2019 at 11:41:54PM +0300, Avraham Shukron wrote: > I have a library which I want to distribute in both shared object and > static library forms. Is that a requirement for your project, or a requirement for the system integrator? With my Debian Developer hat on, I'm always gr

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

2019-09-26 Thread Juan Sanchez
Here is an example where two libraries are created from object files that have only been compiled once: ADD_LIBRARY(symdiff_objects OBJECT ${CXX_SRCS} ${MC_SRCS}) set_property(TARGET symdiff_objects PROPERTY POSITION_INDEPENDENT_CODE ON) ADD_LIBRARY(symdiff_dynamic STATIC $) ADD_LIBRARY(symdiff SH

[CMake] Cmake error

2019-09-26 Thread Enrique González
Dear all, I'm trying to install LLVM with all the projects because I need Clang and the SPIR-V target. I am using cmake like the llvm manual says and it give me this error, could you help me to solve it? I am following the steps from this page: https://llvm.org/docs/GettingStarted.html CMAKE ERR

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

2019-09-26 Thread Avraham Shukron
There is no hard requirement for shipping both static and shared. With the back against the wall I could get away with SHARED only, since it is the most common way the library will be consumed. I wanted to also distribute a static version just for those who want a single, self-contained executable.

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

2019-09-26 Thread J Decker
I ended up using external_project() because unless you also copy the source files, each source file each only gets one set of flags... so if you have different compile options (the config file I suppose) the sources will only build with one or the other. If you copy all of the sources to the CMAKE