t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 1e9f499..1819564 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 12)
-set(CMake_VERSION_PATCH 20180911)
+set(CMake_VER
Hi,
I have a little project that creates a shared library from a pair of assembly
files. I've been trying to follow examples such that the generated library
- has versioning (libFastCompression.1.dylib on Mac or libFastCompression.so.1
on Linux)
- has the full path as its ID on Mac
I get
Michael,
I agree heartily with your frustration concerning how CMake handles compiler
flags -- especially when the FLAG strings seen in cmake-gui don't match the
baseline flags used by the build. I use a heavy handed, old-fashioned approach
to solve this problem.
I ignore all of CMake's
I add it manually each and every time. I have to tell all new developers to
remember to add the flag otherwise they are still sitting after an hour waiting
on our code to compile wondering why it takes so long. Then it hits us, "Oh,
Yeah. Open CMake-Gui and set the /MP flag". I'm frustrated at
Just to be clear I _only_ need it when the generator is Visual Studio so I did
the following:
if(MSVC_IDE)
add_compile_options(/MP)
endif()
>From a clean build directory that did not add it to the CMAKE_CXX_FLAGS when
>viewed in CMake-Gui.
--
Mike Jackson
From: Marc
On 09/11/2018 01:03 PM, Marc CHEVRIER wrote:
The best approach is to use properties (see
https://cmake.org/cmake/help/git-master/manual/cmake-properties.7.html).
At directory level and target level you can use property
'COMPILE_OPTIONS'. These properties can be updated using, respectively
Hello!
Did you consider adding the flag manually during project configuration? I do
not know you use case, but after some thinking about the best way of
achieving multiprocess compilation under MSVS with CMake I decided, that the
simplest, most portable and flexible is to just add this flag
If you set directory property at the top level CMakeList.txt, before any
target definition, all targets will inherit this value.
And, because property 'COMPILE_OPTIONS' supports generator expressions (see
https://cmake.org/cmake/help/v3.12/manual/cmake-generator-expressions.7.html),
you can
Hmm. The idea for the “/MP” flags for those that don’t use Visual Studio is
that it will inform the compiler to use all the cores on the system to compile.
Much like Ninja does automatically and “make -jN” does for makefiles.
Essentially I want to automatically add the “/MP” flag anytime that I
The best approach is to use properties (see
https://cmake.org/cmake/help/git-master/manual/cmake-properties.7.html).
At directory level and target level you can use property
'COMPILE_OPTIONS'. These properties can be updated using, respectively
'add_compile_options' and 'target_compile_options'.
What is the “modern” way to append to CMAKE_CXX_FLAGS? This is the logic that I
would like:
If (MSVC)
Set(CMAKE_CXX_FLAGS ${ CMAKE_CXX_FLAGS} “/MP”)
Endif()
I have always heard that appending to the compile flags in this way is “bad”.
What is the best practice for doing
Le mar. 11 sept. 2018 à 16:10, a écrit :
> Hi,
>
> thank you for your reply. I could solve the problem. The part I didn't
> knew was that static libraries also needed to be compiled with -fPIC.
> I've found a good summary of this topic at
>
Hi,
thank you for your reply. I could solve the problem. The part I didn't
knew was that static libraries also needed to be compiled with -fPIC.
I've found a good summary of this topic at
https://lists.debian.org/debian-devel/2016/05/msg00309.html
I want to share it for those, who also
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 528d7625b89e0343bbf541edd256971493a6e455 (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 b1c8d95dbe97ab2511e08518bf8eee1f5da2e941 (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 e0e56abe3479efddd994cc1a3ee9b8a123111903 (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 c669b59095bf01ab0e254949989677496946ec08 (commit)
via
I believe what you are looking for in the CMake 3.12 improvements to
object libraries. In 3.12 the target_link_libraries command now
supports linking to an object library to embed the object files ( only
on direct dependencies, no propagation of .objs ) and also propagates
usage requirements like
wo...@masterdevops.eu wrote:
> Hi,
>
> I am trying to compile the project libgd
> (https://github.com/libgd/libgd) with the option ENABLE_JPEG enabled.
>
> I.e. first I downloaded the source code of libjpeg-turbo from
> https://sourceforge.net/projects/libjpeg-turbo/files/2.0.0/, compiled it
Hi,
I am trying to compile the project libgd
(https://github.com/libgd/libgd) with the option ENABLE_JPEG enabled.
I.e. first I downloaded the source code of libjpeg-turbo from
https://sourceforge.net/projects/libjpeg-turbo/files/2.0.0/, compiled it
and afterwards I started to compile libgd
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 78d165c9905f73237229497772769a6dc2c32982 (commit)
via
21 matches
Mail list logo
