t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index f2b87cb..31a220f 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 14)
-set(CMake_VERSION_PATCH 20190509)
+set(CMake_VER
My team sometimes discovers bugs in our build system where modifying one
particular file doesn't trigger a rebuild of some dependent file.
While our continuous integration system (Jenkins) catches problems when
building the whole project, we don't currently have any way to detect problems
with
The goal would be to upstream the compiler changes to cmake so that
all users could benefit from the improved compiler detection :)
I would look at the FindMPI docs on locating the correct mpi compiler:
https://cmake.org/cmake/help/v3.14/module/FindMPI.html#variables-for-locating-mpi
. It looks
Hi Nick,
Not sure if it is relevant for you, but for other who will search.
I have the same problem.
What I found:
1. When you issue "cmake --build", it runs following command line:
msbuild ALL_BUILD.vcxproj /p:Platform=Win32 ...
So it is not a solution file, that have rules to match
ummh, sooo... h, do you like... cheese?
On 5/9/19 7:21 AM, Stefan Fendt wrote:
Am 07.05.2019 um 20:37 schrieb Angel Campoverde:
Next time please ask what computer I am using.
*What*? Really? *Please* give this a second thought...
Stefan
--
Powered by www.kitware.com
Please keep messages
Am 07.05.2019 um 20:37 schrieb Angel Campoverde:
> Next time please ask what computer I am using.
*What*? Really? *Please* give this a second thought...
Stefan
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
