1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
#
# This file is part of the GROMACS molecular simulation package.
#
# Copyright 2014- The GROMACS Authors
# and the project initiators Erik Lindahl, Berk Hess and David van der Spoel.
# Consult the AUTHORS/COPYING files and https://www.gromacs.org for details.
#
# GROMACS is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public License
# as published by the Free Software Foundation; either version 2.1
# of the License, or (at your option) any later version.
#
# GROMACS is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with GROMACS; if not, see
# https://www.gnu.org/licenses, or write to the Free Software Foundation,
# Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
#
# If you want to redistribute modifications to GROMACS, please
# consider that scientific software is very special. Version
# control is crucial - bugs must be traceable. We will be happy to
# consider code for inclusion in the official distribution, but
# derived work must not be called official GROMACS. Details are found
# in the README & COPYING files - if they are missing, get the
# official version at https://www.gromacs.org.
#
# To help us fund GROMACS development, we humbly ask that you cite
# the research papers on the package. Check out https://www.gromacs.org.
# "tests" target builds all the separate test binaries.
add_custom_target(tests)
# "run-ctest" is an internal target that actually runs the tests.
# This is necessary to be able to add separate targets that execute as part
# of 'make check', but are ensured to be executed after the actual tests.
add_custom_target(run-ctest
COMMAND ${CMAKE_CTEST_COMMAND} --output-on-failure
COMMENT "Running all tests"
USES_TERMINAL VERBATIM
DEPENDS run-physval-sims)
add_dependencies(run-ctest tests)
# "check-all" target builds and runs all tests, simulating the physical validation systems first.
add_custom_target(check-all DEPENDS run-ctest)
# "run-ctest-nophys" is an internal target that actually runs the tests analogously to "run-ctest".
# It runs all tests except the physical validation tests.
add_custom_target(run-ctest-nophys
COMMAND ${CMAKE_CTEST_COMMAND} --output-on-failure -E physicalvalidationtests
COMMENT "Running all tests except physical validation"
USES_TERMINAL VERBATIM)
add_dependencies(run-ctest-nophys tests)
# "check" target builds and runs all tests except physical validation .
add_custom_target(check DEPENDS run-ctest-nophys)
# "run-ctest-phys" is an internal target that actually runs the tests analogously to "run-ctest".
# It only runs the physical validation tests.
add_custom_target(run-ctest-phys
COMMAND ${CMAKE_CTEST_COMMAND} --output-on-failure -R physicalvalidationtests
COMMENT "Running physical validation tests"
USES_TERMINAL VERBATIM
DEPENDS run-physval-sims)
# "run-ctest-phys-analyze" is the equivalent to "run-ctest-phys" not running the physical validation simulations.
add_custom_target(run-ctest-phys-analyze
COMMAND ${CMAKE_CTEST_COMMAND} --output-on-failure -R physicalvalidationtests
COMMENT "Running physical validation tests"
USES_TERMINAL VERBATIM
DEPENDS gmx)
# "check-phys" target runs only physical validation tests, simulating the systems first.
add_custom_target(check-phys DEPENDS run-ctest-phys)
# "check-phys-analyze" target runs only physical validation tests, without simulating the systems first.
add_custom_target(check-phys-analyze DEPENDS run-ctest-phys-analyze)
# Calling targets "check-all" and "check-phys" does not make much sense if -DGMX_PHYSICAL_VALIDATION=OFF
if(NOT GMX_PHYSICAL_VALIDATION)
add_custom_target(missing-phys-val-phys
COMMAND ${CMAKE_COMMAND} -E echo "NOTE: You called the target `check-phys`, but ran cmake with\
`-DGMX_PHYSICAL_VALIDATION=OFF`. The physical validation tests are therefore unavailable,\
and this target is not testing anything."
DEPENDS run-ctest-phys
COMMENT "No physical validation" VERBATIM)
add_dependencies(check-phys missing-phys-val-phys)
add_custom_target(missing-phys-val-phys-analyze
COMMAND ${CMAKE_COMMAND} -E echo "NOTE: You called the target `check-phys-analyze`, but ran cmake with\
`-DGMX_PHYSICAL_VALIDATION=OFF`. The physical validation tests are therefore unavailable,\
and this target is not testing anything."
DEPENDS run-ctest-phys-analyze
COMMENT "No physical validation" VERBATIM)
add_dependencies(check-phys-analyze missing-phys-val-phys)
add_custom_target(missing-phys-val-all
COMMAND ${CMAKE_COMMAND} -E echo "NOTE: You called the target `check-all`, but ran cmake with\
`-DGMX_PHYSICAL_VALIDATION=OFF`. The physical validation tests are therefore unavailable,\
and this target is equivalent to a simple `make check`."
DEPENDS run-ctest
COMMENT "No physical validation" VERBATIM)
add_dependencies(check-all missing-phys-val-all)
endif()
# Global property for collecting notices to show at the end of the targets.
# Expanded to avoid to show messages about physical validation when only
# the other tests are ran, and vice-versa.
set_property(GLOBAL PROPERTY GMX_TESTS_NOTICE)
function (gmx_add_missing_tests_notice TEXT)
set_property(GLOBAL APPEND PROPERTY GMX_TESTS_NOTICE ${TEXT})
endfunction()
function (gmx_create_missing_tests_notice_target)
get_property(_text GLOBAL PROPERTY GMX_TESTS_NOTICE)
set(_cmds)
foreach (_line ${_text})
list(APPEND _cmds COMMAND ${CMAKE_COMMAND} -E echo "NOTE: ${_line}")
endforeach()
list(LENGTH _cmds n)
# checking whether any messages should be displayed
if(${n})
# Needs to be separated in two targets: should be ran *either* after run-ctest-nophys,
# *or* after run-ctest. I don't think there's a way to do that with a single target.
add_custom_target(missing-tests-notice
${_cmds}
DEPENDS run-ctest-nophys
COMMENT "Some tests not available" VERBATIM)
add_dependencies(check missing-tests-notice)
add_custom_target(missing-tests-notice-all
${_cmds}
DEPENDS run-ctest
COMMENT "Some tests not available" VERBATIM)
add_dependencies(check-all missing-tests-notice-all)
endif()
endfunction()
|
