Hi Bill,
Thanks a lot for your quick response! Using your idea I could set the
Fortran module directory per module target, and add those directories as
target_include_directories to the executables. Worked like a charm!
Lukas
PS. As example, I adapted my cat/dog CMakeLists.txt to this to get to
We are pleased to announce that CMake 3.16.5 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.5 since 3.16.4:
On 04/03/2020 09:24, Lukas van de Wiel wrote:
we are running a Fortran code containing several dozen modules. These
are build in two versions, differentiated by #ifdef statements. The
archive files of the two versions are being kept apart by different
file names, but the .mod files have fixed
Dear more experienced cmake user,
we are running a Fortran code containing several dozen modules. These are
build in two versions, differentiated by #ifdef statements. The archive
files of the two versions are being kept apart by different file names, but
the .mod files have fixed names, based on
вт, 3 мар. 2020 г. в 07:52, Ray Satiro via CMake :
>
> I am building libssh with cmake. I have two versions of OpenSSL on my
> system and need libssh to use the later version of OpenSSL, which is in
> /usr/local/ssl/lib. I need that rpath both before and after install, as
> libssh should always
