t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 89858aa..9bef298 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 15)
-set(CMake_VERSION_PATCH 20190617)
+set(CMake_VER
On Linux (Debian Testing) with CMake 3.13.2 (which I built myself)
I have a case where apparently
target_link_libraries( /usr/lib/x86_64-linux-gnu/libm.so)
results in an actual link option "-lm". Is this an exception to the
rule documented at
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
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
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
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 77e59e442d110b2cb3c5d206e79f631175805974 (commit)
via
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
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
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
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 dad271e8b7eec9ce781bccb9e7e7c9ed4f55003c (commit)
via
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 2c2c575383c049a312a9a276e195df6699364530 (commit)
via
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 3d8216330da76bac8267d64d4940af0b05e502a9 (commit)
via
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 0da805bff39f5e465d48f678f3b49b3dc738ab9f (commit)
via
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
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
15 matches
Mail list logo
