If I specify an empty value for filename, I get the behavior of relative
path, and var turns into CMAKE_CURRENT_SOURCE_DIR. It seems like if I put
an empty file I should get back an empty output.
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
htt
I have been successfully using CMake's GTEST_ADD_TESTS to run GTest
TEST and TEST_F blocks defined in a source file. However, I now need
to pass some arguments (filenames that I want CMake to produce
including things like ${CMAKE_SOURCE_DIR}) to the GTests, and it seems
like the way to do this is w
Petr,
Thanks for the info. I'm working on getting the builds to work exactly like I
want for both native *nix and cross-compile Windows builds, so it's a learning
process. I do appreciate your info.
vadtecvad...@vadtec.net
On Thu, 04 Feb 2016 01:49:12 -0600 Petr Kmoch
Brad,
I want to confirm that your patch below fixed the issue that I reported.
Thank you!
-kt
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Friday, February 05, 2016 7:32 AM
To: Thompson, KT
Cc: cmake@cmake.org; Stephen Kelly
Subject: Re: [CMake] cmake 3.5.0
On 02/04/2016 04:00 PM, Thompson, KT wrote:
> If I run ‘make VERBOSE=1’ with CMake-3.4.3, I see the following command:
>
> cmake -E cmake_copy_f90_mod src/dir1/dir2/myf90file
> src/dir1/dir2/CMakeFiles/Lib_FC_f90sub.dir/myf90file.mod.stamp Intel
>
> but with CMake-3.5.0-rc1, I have this command
Dear all,
do you know a best practice on how to specify compiler flags without knowing in
advance which compiler will be used?
Its about Fortran projects, where I e.g. want to explicitly enable the
preprocessor, or make all default real values 8 byte wide. This could be done
as such:
if(${CMAKE_