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();
exit(strstr(\"\\\0test\",
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 along
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 th
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 cross-compi
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 I
