| commit | 382b492ae08d6e47ede55f1a0319be9d99b7b67a | |
| author | Mark Abraham <mark.j.abraham@gmail.com> | |
| Tue, 19 Dec 2017 07:25:06 +0000 (19 18:25 +1100) | ||
| committer | Erik Lindahl <erik.lindahl@gmail.com> | |
| Fri, 5 Jan 2018 14:35:58 +0000 (5 15:35 +0100) | ||
| tree | a08ccefb967a2e37cce776c351ecf6417288b3b0 | treesnapshot (tar.gz zip) |
| parent | 2002cfdecf30de2677944da27cfc65ee88f58f96 | commitdiff |
Remove FindCUDA from source tarball
When we decided to bundle FindCUDA.cmake and supporting files to keep
our developer and Jenkins builds free of warnings, we did not take
care to ensure that the user gets the behaviour from their cmake,
since the combination of their cmake and its FindCUDA.cmake is much
more likely to work correctly than their cmake and FindCUDA.cmake from
cmake 3.4.3.
The testing of the release tarball as part of the release workflow
will ensure that we don't silently ship a broken CUDA build.
Refs #2276
Change-Id: I9ed6fa97921eb5c3ce3b4a6ecc401b4dd26e1251
When we decided to bundle FindCUDA.cmake and supporting files to keep
our developer and Jenkins builds free of warnings, we did not take
care to ensure that the user gets the behaviour from their cmake,
since the combination of their cmake and its FindCUDA.cmake is much
more likely to work correctly than their cmake and FindCUDA.cmake from
cmake 3.4.3.
The testing of the release tarball as part of the release workflow
will ensure that we don't silently ship a broken CUDA build.
Refs #2276
Change-Id: I9ed6fa97921eb5c3ce3b4a6ecc401b4dd26e1251
| cmake/gmxCPackUtilities.cmake | diffblobblamehistory |