Re: [CMake] Mingw64: add a statically linked library adds libstdc++ dependency

2019-06-17 Thread William Zeitler
What finally worked was: set(CMAKE_CXX_STANDARD_LIBRARIES "-static-libgcc -static-libstd++ ${CMAKE_CXX_STANDARD_LIBRARIES}) if(MINGW)     set (CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -Wl,-Bstatic,--whole-archive -lwinpthread -Wl,--no-whole-archive") endif() Thanks! On 6/17/19 02:

Re: [CMake] Multiple exports for a target installation

2019-06-17 Thread Shoaib Meenai
Thank you! When you say having an export set that the other exports then depend on, do you mean the COMPONENT option of the install(EXPORT) signature, or something else? (Sadly the project I’m working with is still on CMake 3.4.3, whose documentation says something very different for the COMPON

Re: [CMake] Why do executables link static libs that shared libs were built from?

2019-06-17 Thread Paul Smith
On Mon, 2019-06-17 at 11:43 +0200, Eric Noulard wrote: > Yes you are right and I know that, but AFAIK when (with CMake) you > TLL a shared lib to a static lib. You do not end up with any of the > static lib symbol in the shared lib. That can't be true, unless cmake is adding fancy linker options t

Re: [CMake] Specifying name of library file on CMake command line?

2019-06-17 Thread Kyle Edwards
On Mon, 2019-06-17 at 13:47 +, Osman Zakir wrote: > I want to know how to specify the name of a library I file I want to > link against.  How do I do this?  I wanted to build a library with a > static runtime and static libs; it requires linking against a Boost > library which I did build with

[CMake] Specifying name of library file on CMake command line?

2019-06-17 Thread Osman Zakir
I want to know how to specify the name of a library I file I want to link against. How do I do this? I wanted to build a library with a static runtime and static libs; it requires linking against a Boost library which I did build with static runtime but when I tried to build it, I had linker e

[CMake] getting compiler's include paths

2019-06-17 Thread jl forums
Hi, I want to create a full tag file and for this require to know the compiler full include path... there is a way to had custom includes path but didn't found any variables for the include path for example : $ gcc-8 -v -x c -E /dev/null Using built-in specs. [] ignoring nonexistent direct

Re: [CMake] Why do executables link static libs that shared libs were built from?

2019-06-17 Thread Eric Noulard
Le lun. 17 juin 2019 à 02:01, Paul Smith a écrit : > On Sun, 2019-06-16 at 21:42 +0200, Eric Noulard wrote: > > Le dim. 16 juin 2019 à 18:26, Paul Smith a > > écrit : > > > But, that's not the only way to use shared libraries. I'm trying > > > to collect a number of static libraries with differ

Re: [CMake] Mingw64: add a statically linked library adds libstdc++ dependency

2019-06-17 Thread Eric Dönges
On 15.06.19 21:33, William Zeitler wrote: > In the example below, two lines are marked "COMMENT ME OUT": one in > hello_c/main.cpp and the other in hello_c/CMakeLists.txt. If you comment > these out, the reference to the hello_lib library is removed; the > project builds and the executable executes