t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 616e7d8..94e60fc 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 13)
-set(CMake_VERSION_PATCH 20181115)
+set(CMake_VER
I have an older 3rd party (that is no longer supported) cmake file, that relies
on the CMP0053 OLD setting
Since I have moved to 3.12, Im getting the warning that its deprecated etc...
SC_CHECK_BROKEN_FUNC(
strstr "
extern int strstr();
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 b32474322907fcd2658ad964847fc62b02659517 (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 1763f0428193cd6e28af4e49131516299acdf3b7 (commit)
via
Hi,
how does the project command looks inside your CMakeLists.txt file?
project( LANGUAGES Fortran) should work
Cheers Volker
Am 15.11.2018 um 14:35 schrieb Magne Rudshaug:
Hi,
In some of my Fortran projects I have Windows resource files of type
.rc associated. Just listing this file
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 64df9ef33a2f4eb9ef0cb17a2844308d9c7f7034 (commit)
via
Hi,
In some of my Fortran projects I have Windows resource files of type .rc
associated. Just listing this file along with the other Fortran source files
doesn't work.
In this case the project is interpreted as a C/C++ project. How can I get cmake
to treat the .rc file correctly (compiled by
At MacOS, in 99% cases, the build task always needs to setup the variables
- CMAKE_OSX_TARGET
- CMAKE_OSX_DEPLOYMENT_TARGET
This 2 variables are important. The CMAKE_OSX_TARGET would define the
minimal set of API during compilation, and this affects the built binary.
The second is the path
Le jeu. 15 nov. 2018 à 09:47, Stéphane Ancelot a
écrit :
> I agree. That was a debug snippet...but is wrong ... I setted up again the
> toolchain, but does not help.
>
If you are using a proper toolchain for 32bit compilation.
It looks like a bug in the find_package for Python in the
I agree. That was a debug snippet...but is wrong ... I setted up again
the toolchain, but does not help.
So, I know where are include_dirs and libs for 32 bits cross
compiling, I have to hardcode it like this ?
add_library(python SHARED IMPORTED)
set_target_properties( python PROPERTIES
10 matches
Mail list logo