2 # This file is part of the GROMACS molecular simulation package.
4 # Copyright (c) 2014,2015,2016,2017,2018 by the GROMACS development team.
5 # Copyright (c) 2019,2020, by the GROMACS development team, led by
6 # Mark Abraham, David van der Spoel, Berk Hess, and Erik Lindahl,
7 # and including many others, as listed in the AUTHORS file in the
8 # top-level source directory and at http://www.gromacs.org.
10 # GROMACS is free software; you can redistribute it and/or
11 # modify it under the terms of the GNU Lesser General Public License
12 # as published by the Free Software Foundation; either version 2.1
13 # of the License, or (at your option) any later version.
15 # GROMACS is distributed in the hope that it will be useful,
16 # but WITHOUT ANY WARRANTY; without even the implied warranty of
17 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
18 # Lesser General Public License for more details.
20 # You should have received a copy of the GNU Lesser General Public
21 # License along with GROMACS; if not, see
22 # http://www.gnu.org/licenses, or write to the Free Software Foundation,
23 # Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
25 # If you want to redistribute modifications to GROMACS, please
26 # consider that scientific software is very special. Version
27 # control is crucial - bugs must be traceable. We will be happy to
28 # consider code for inclusion in the official distribution, but
29 # derived work must not be called official GROMACS. Details are found
30 # in the README & COPYING files - if they are missing, get the
31 # official version at http://www.gromacs.org.
33 # To help us fund GROMACS development, we humbly ask that you cite
34 # the research papers on the package. Check out http://www.gromacs.org.
36 # Sets version information variables and provides CMake functions for
37 # generating files based on them
39 # This script provides the following basic version variables that need to be
40 # maintained manually:
41 # GMX_VERSION_MAJOR Major version number.
42 # GMX_VERSION_PATCH Patch version number.
43 # Should always be defined: zero for, e.g., 2016.
44 # GMX_VERSION_SUFFIX String suffix to add to numeric version string.
45 # "-dev" is automatically added when not building from a source package,
46 # and does not need to be kept here. This mechanism is not quite enough
47 # for building a tarball, but setting the CMake cache variable
48 # GMX_BUILD_TARBALL=on will suppress the addition of "-dev" to the
50 # LIBRARY_SOVERSION_MAJOR so major version for the built libraries.
51 # Should be increased for each binary incompatible release. In GROMACS,
52 # the typical policy is to increase it at the start of the development
53 # cycle for each major/minor version change, but not for patch releases,
54 # even if the latter may not always be fully binary compatible.
55 # Table of historical values
63 # LIBRARY_SOVERSION_MINOR so minor version for the built libraries.
64 # Should be increased for each release that changes only the implementation.
65 # In GROMACS, the typical policy is to increase it for each patch version
66 # change, even if they may not always be fully binary compatible.
67 # If it is somehow clear that the ABI implementation has not changed
68 # in a patch release, this variable should not increase. Release candidate
69 # and beta versions will not increase this number, since nobody should
70 # write code against such versions.
71 # LIBRARY_VERSION Full library version.
72 # REGRESSIONTEST_BRANCH For builds not from source packages, name of the
73 # regressiontests branch at gerrit.gromacs.org whose HEAD can test this
74 # code, *if* this code is recent enough (i.e., contains all changes from
75 # the corresponding code branch that affects the regression test
76 # results). Even after a release branch is forked for the source
77 # repository, the correct regressiontests branch can still be master,
78 # because we do not fork it until behaviour needs to change.
79 # REGRESSIONTEST_MD5SUM
80 # The MD5 checksum of the regressiontest tarball. Only used when building
81 # from a source package.
83 # ID collected from Zenodo connected to the doi for a released version
84 # used to identify the source when building an official released version.
85 # This ID is used for the source code tarball.
87 # Same as above, but for the reference manual.
88 # They are collected into a single section below.
89 # The following variables are set based on these:
90 # GMX_VERSION String composed from GMX_VERSION_* numeric variables
91 # above. Example: 4.6.1, 5.0, 2016
92 # GMX_VERSION_STRING String with GMX_VERSION suffixed with the given
93 # suffix and possibly "-dev" for builds not from a source package.
94 # GMX_VERSION_NUMERIC Numeric version number (e.g., 40601 for 4.6.1, 20160001 for 2016.1).
95 # GMX_API_VERSION Numeric API version.
96 # This is currently set automatically to GMX_VERSION_NUMERIC, but may
97 # become manually maintained in the future if there will be releases
98 # where the API does not change, but programs/libraries do.
99 # In such a case, this should be the first version where the current API
101 # REGRESSIONTEST_VERSION For source packages, version number of the
102 # matching regressiontests tarball. Not used for builds not from source
104 # The latter two are used to generate gromacs/version.h to allow software
105 # written against the GROMACS API to provide some #ifdef'ed code to support
106 # multiple GROMACS versions.
108 # This script also declares machinery to generate and obtain version
109 # information from a git repository. This is enabled by default if the source
110 # tree is a git, but can be disabled with
111 # GMX_GIT_VERSION_INFO Advanced CMake variable to disable git
112 # version info generation.
113 # If the version generation is disabled, then the source and manual doi
114 # will be based on the stored values for the ID.
115 # The main interface to this machinery is the gmx_configure_version_file()
116 # CMake function. The signature is
117 # gmx_configure_version_file(<input> <output>
120 # [COMMENT <comment>])
121 # <input> Specify the input and output files as for configure_file().
122 # <output> The configuration is done with configure_file(... @ONLY) with
123 # the following variables defined (as well as all the
124 # GMX_VERSION* variables from above):
125 # GMX_VERSION_STRING_FULL
126 # GMX_VERSION_FULL_HASH
127 # GMX_VERSION_CENTRAL_BASE_HASH
128 # The output file is created during build time, so any dependent
129 # targets should specify it as a dependency.
130 # REMOTE_HASH Currently, this has no effect, but it signifies that the
131 # <input> file is using the CENTRAL_BASE_HASH variable.
132 # This variable is much more expensive to initialize than the
133 # others, so this allows local changes in this file to only
134 # compute that value when required if that becomes necessary.
135 # TARGET By default, this function uses add_custom_command() to
136 # generate the output file. If TARGET is specified, then
137 # add_custom_target() is used to create a target with the given
138 # name <target> that runs this custom command. Use this if
139 # the same file will be used for multiple downstream targets,
140 # or if the explicit target for the file is otherwise
142 # COMMENT Set a custom comment to be shown when building the rule
143 # (see add_custom_command(... COMMENT <comment>)).
144 # As an alternative to using this script, also the following variables are
145 # provided (can be useful when generating more complex CMake scripts that do
147 # VERSION_INFO_CMAKE_SCRIPT
148 # Absolute path to a CMake script that can be included using include()
149 # to declare the GMX_VERSION_* variables documented for
150 # gmx_configure_version_file().
152 # If a custom command depends on VERSION_INFO_CMAKE_SCRIPT, then it
153 # should add ${VERSION_INFO_DEPS} to its DEPENDS list to get the
154 # appropriate dependencies.
155 # TODO: If someone wants to add a custom target that depends on
156 # VERSION_INFO_CMAKE_SCRIPT, a separate variable may be needed for those
159 # The version string printed by 'gmx -version' (and also printed in the startup
160 # header) can provide useful information for, e.g., diagnosing bug reports and
161 # identifying what exact version the user was using. The following formats are
162 # possible (with examples given for a particular version):
163 # 2018.1 Plain version number without any suffix signifies a build from
164 # a released source tarball.
165 # 2018.1-dev '-dev' suffix signifies all other builds. If there is no other
166 # information, either the user built the code outside any git
167 # repository, or disabled the version info generation.
168 # 2018.1-dev-YYYYMMDD-1234abc
169 # The YYYYMMDD part shows the commit date (not author date) of
170 # the HEAD commit from which the code was built. The abbreviated
171 # hash is the hash of that commit (the full hash is available in
172 # 'gmx -version' output).
173 # If the HEAD hash is not identified as coming from branches in
174 # "authoritative" GROMACS repositories, 'gmx -version' will show
175 # the nearest ancestor commit that is identified as such (but see
176 # the '-local' and '-unknown' suffixes below).
177 # 2018.1-dev-YYYYMMDD-1234abc-dirty
178 # As above, but there were local modifications in the source tree
179 # when the code was built.
180 # 2018.1-dev-YYYYMMDD-1234abc-unknown
181 # As above, but there were no remotes in the repository that
182 # could be identified as "authoritative" GROMACS repositories.
183 # This happens if the code is not cloned from git.gromacs.org
184 # or gerrit.gromacs.org.
185 # 2018.1-dev-YYYYMMDD-1234abc-local
186 # As above, but there were no commits in the recent history of
187 # the branch that could be identified as coming from
188 # "authoritative" GROMACS repositories. This should be
191 # Other variables set here are not intended for use outside this file.
192 # The scripts gmxGenerateVersionInfo.cmake and gmxConfigureVersionInfo.cmake
193 # are used internally by this machinery, as well as VersionInfo.cmake.cmakein.
195 #####################################################################
196 # Manually maintained version info
198 # The GROMACS convention is that these are the version number of the next
199 # release that is going to be made from this branch.
200 set(GMX_VERSION_MAJOR 2021)
201 set(GMX_VERSION_PATCH 0)
202 # The suffix, on the other hand, is used mainly for betas and release
203 # candidates, where it signifies the most recent such release from
204 # this branch; it will be empty before the first such release, as well
205 # as after the final release is out.
206 set(GMX_VERSION_SUFFIX "")
208 # Conventionally with libtool, any ABI change must change the major
209 # version number, the minor version number should change if it's just
210 # the implementation that has been altered, and the third number
211 # counts the number of old major versions that will still run if
212 # linked to this library (i.e. it is not a patch number). See the
213 # above descriptions of LIBRARY_SOVERSION_* for policy for changes
214 # here. The important thing is to minimize the chance of third-party
215 # code being able to dynamically link with a version of libgromacs
216 # that might not work.
217 set(LIBRARY_SOVERSION_MAJOR 6)
218 set(LIBRARY_SOVERSION_MINOR 0)
219 set(LIBRARY_VERSION ${LIBRARY_SOVERSION_MAJOR}.${LIBRARY_SOVERSION_MINOR}.0)
221 #####################################################################
222 # General version management based on manually set numbers
224 if (GMX_VERSION_PATCH)
225 set(GMX_VERSION "${GMX_VERSION_MAJOR}.${GMX_VERSION_PATCH}")
227 set(GMX_VERSION "${GMX_VERSION_MAJOR}")
229 set(GMX_VERSION_STRING "${GMX_VERSION}${GMX_VERSION_SUFFIX}")
231 # If you are making a custom fork of GROMACS, please describe your
232 # fork, perhaps with its version number, in the value of
233 # GMX_VERSION_STRING_OF_FORK here. This string will appear in the
234 # header of log files that mdrun writes. This will help you, your
235 # users, your system administrators, your maintainers and the
236 # maintainers of GROMACS core understand how to troubleshoot and
237 # reproduce potential problems.
239 # If you are distributing a patch to GROMACS, then this change would
240 # be great as part of your patch. Otherwise for personal use, you can
241 # also just set a CMake cache variable.
242 set(GMX_VERSION_STRING_OF_FORK "" CACHE INTERNAL
243 "Version string for forks of GROMACS to set to describe themselves")
244 mark_as_advanced(GMX_VERSION_STRING_OF_FORK)
245 if (GMX_VERSION_STRING_OF_FORK)
246 set(GMX_VERSION_STRING "${GMX_VERSION_STRING}-${GMX_VERSION_STRING_OF_FORK}")
249 option(GMX_BUILD_TARBALL "Build tarball without -dev version suffix" OFF)
250 mark_as_advanced(GMX_BUILD_TARBALL)
251 # If run with cmake -P, the -dev suffix is managed elsewhere.
252 if (NOT SOURCE_IS_SOURCE_DISTRIBUTION AND
253 NOT GMX_BUILD_TARBALL AND
254 NOT CMAKE_SCRIPT_MODE_FILE)
255 set(GMX_VERSION_STRING "${GMX_VERSION_STRING}-dev")
258 set(REGRESSIONTEST_VERSION "${GMX_VERSION_STRING}")
259 set(REGRESSIONTEST_BRANCH "master")
260 # Run the regressiontests packaging job with the correct pakage
261 # version string, and the release box checked, in order to have it
262 # build the regressiontests tarball with all the right naming. The
263 # naming affects the md5sum that has to go here, and if it isn't right
264 # release workflow will report a failure.
265 set(REGRESSIONTEST_MD5SUM "b75c3b1bac0e4114e236f049fc7f1f1c" CACHE INTERNAL "MD5 sum of the regressiontests tarball for this GROMACS version")
267 math(EXPR GMX_VERSION_NUMERIC
268 "${GMX_VERSION_MAJOR}*10000 + ${GMX_VERSION_PATCH}")
269 set(GMX_API_VERSION ${GMX_VERSION_NUMERIC})
271 # If run with cmake -P from releng scripts, print out necessary version info
273 if (CMAKE_SCRIPT_MODE_FILE)
274 message("{ \"version\": \"${GMX_VERSION_STRING}\", \"regressiontest-md5sum\": \"${REGRESSIONTEST_MD5SUM}\" }")
278 # Set those values only in release versions, after getting the identifiers
279 # from Zenodo for the manual and source code
280 # Has to be done by hand before every final release
281 # Use force to override anything given as a cmake command line input
282 # Actual input depends on the GMX_VERSION_STRING_OF_FORK variable being set or not.
283 # If it is set, we always default to an empty string, otherwise to the value set for the release build.
284 if (GMX_VERSION_STRING_OF_FORK)
285 set(GMX_MANUAL_DOI_INTERNAL "")
286 set(GMX_SOURCE_DOI_INTERNAL "")
288 set(GMX_MANUAL_DOI_INTERNAL "") # Set correct doi string here
289 set(GMX_SOURCE_DOI_INTERNAL "") # Set correct doi string here
291 set(GMX_MANUAL_DOI ${GMX_MANUAL_DOI_INTERNAL} CACHE INTERNAL "reserved doi for GROMACS manual" FORCE)
292 set(GMX_SOURCE_DOI ${GMX_SOURCE_DOI_INTERNAL} CACHE INTERNAL "reserved doi for GROMACS source code" FORCE)
294 #####################################################################
295 # git version info management
297 # There can be clusters where git and CMake can run on nodes where the other is
298 # not available, accessing the same source tree.
299 # Should be unlikely, but doesn't hurt to check.
300 set(_git_info_default OFF)
301 if (SOURCE_IS_GIT_REPOSITORY)
304 set(_git_info_default ON)
307 option(GMX_GIT_VERSION_INFO "Generate git version information" ${_git_info_default})
308 mark_as_advanced(GMX_GIT_VERSION_INFO)
309 # Detect preconditions for version info generation if it is requested.
310 if (GMX_GIT_VERSION_INFO)
311 if (NOT SOURCE_IS_GIT_REPOSITORY)
313 "Cannot generate git version information from source tree not under git. "
314 "Set GMX_GIT_VERSION_INFO=OFF to proceed.")
316 # We need at least git v1.5.3 be able to parse git's date output.
317 if (NOT GIT_FOUND OR GIT_VERSION_STRING VERSION_LESS "1.5.3")
319 "No compatible git version found (>= 1.5.3 required). "
320 "Won't be able to generate development version information. "
321 "Set GMX_GIT_VERSION_INFO=OFF to proceed.")
325 include(gmxCustomCommandUtilities)
327 # The first two are also for use outside this file, encapsulating the details
328 # of how to use the generated VersionInfo.cmake.
329 set(VERSION_INFO_CMAKE_FILE ${PROJECT_BINARY_DIR}/VersionInfo.cmake)
330 set(VERSION_INFO_DEPS ${VERSION_INFO_CMAKE_FILE})
331 # Capture the location of the necessary files in internal variables for use in
332 # the function below.
333 set(VERSION_INFO_CMAKEIN_FILE ${CMAKE_CURRENT_LIST_DIR}/VersionInfo.cmake.cmakein)
334 set(VERSION_INFO_CONFIGURE_SCRIPT ${CMAKE_CURRENT_LIST_DIR}/gmxConfigureVersionInfo.cmake)
335 # A set of directories to scan for calculating the hash of source files.
336 set(SET_OF_DIRECTORIES_TO_CHECKSUM "src")
337 list(APPEND SET_OF_DIRECTORIES_TO_CHECKSUM "python_packaging")
338 # Due to the limitations for passing a list as arguments, we make the directories a string here
339 string(REPLACE ";" ":" DIRECTORIES_TO_CHECKSUM_STRING "${SET_OF_DIRECTORIES_TO_CHECKSUM}")
341 # Rules to create the VersionInfo.cmake file.
342 # For git info, the sequence is:
343 # 1. (configure time) VersionInfo.cmake.cmakein -> VersionInfo-partial.cmake.cmakein
344 # - Set all variables that are known at configure time.
345 # 2. (build time) VersionInfo-partial.cmake.cmakein -> VersionInfo.cmake
346 # - Set variables that may change as result of repository state changes
347 # (i.e., everything that requires running git).
348 # - Runs every time as a git-version-info target, but the output file
349 # timestamp only changes if its contents actually change.
350 # - Depending on the native build system, this may run once per build
351 # or once per each time it is required for step 3.
352 # 3. (build time) VersionInfo.cmake -> other files
353 # - Set variables in files specified with gmx_configure_version_file()
354 # using the values generated in step 2.
355 # - Each file runs as a custom command that depends on the previous
356 # steps, and runs only if the VersionInfo.cmake file is newer than the
358 # Without git info, the sequence is:
359 # 1. (configure time) VersionInfo.cmake.cmakein -> VersionInfo.cmake
360 # - Everything is known at configure time, so the output is generated
361 # immediately with all variables set (git info will be empty).
362 # 2. (build time) VersionInfo.cmake -> other files
363 # - As with git info, processes files from gmx_configure_version_file().
364 # - These are again custom commands that depend on the output from
365 # step 1, so they get regenerated only when the static version info
368 # Configure information known at this time into a partially filled
370 set(VERSION_INFO_CMAKEIN_FILE_PARTIAL
371 ${PROJECT_BINARY_DIR}/VersionInfo-partial.cmake.cmakein)
372 # Leave these to be substituted by the targets below.
373 set(GMX_VERSION_STRING_FULL "\@GMX_VERSION_STRING_FULL\@")
375 if (GMX_GIT_VERSION_INFO)
376 # Leave these to be substituted by the custom target below.
377 # Specific for building from git.
378 set(GMX_VERSION_FULL_HASH "\@GMX_VERSION_FULL_HASH\@")
379 set(GMX_VERSION_CENTRAL_BASE_HASH "\@GMX_VERSION_CENTRAL_BASE_HASH\@")
380 # If generating the version info, create a target that runs on every build
381 # and does the actual git calls, storing the results into a CMake script.
382 # This needs to be run at build time to update the version information
383 # properly when the git hash changes, but the build system does not.
384 # All targets added by gmx_configure_version_file() use the information
385 # from this script to get their variables from, removing the need to run
386 # git multiple times and simplifying reuse for other purposes.
387 gmx_add_custom_output_target(git-version-info RUN_ALWAYS
388 OUTPUT ${VERSION_INFO_CMAKE_FILE}
389 COMMAND ${CMAKE_COMMAND}
390 -D GIT_EXECUTABLE=${GIT_EXECUTABLE}
391 -D PROJECT_VERSION=${GMX_VERSION_STRING}
392 -D PROJECT_SOURCE_DIR=${PROJECT_SOURCE_DIR}
393 -D VERSION_CMAKEIN=${VERSION_INFO_CMAKEIN_FILE_PARTIAL}
394 -D VERSION_OUT=${VERSION_INFO_CMAKE_FILE}
395 -P ${CMAKE_CURRENT_LIST_DIR}/gmxGenerateVersionInfo.cmake
396 WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
397 COMMENT "Generating git version information")
398 list(APPEND VERSION_INFO_DEPS git-version-info)
400 # Leave these to be substituted by the custom target below.
401 # Specific for building from source tarball.
402 set(GMX_RELEASE_SOURCE_FILE_CHECKSUM "\@GMX_RELEASE_SOURCE_FILE_CHECKSUM\@")
403 set(GMX_CURRENT_SOURCE_FILE_CHECKSUM "\@GMX_CURRENT_SOURCE_FILE_CHECKSUM\@")
404 gmx_add_custom_output_target(release-version-info RUN_ALWAYS
405 OUTPUT ${VERSION_INFO_CMAKE_FILE}
406 COMMAND ${CMAKE_COMMAND}
407 -D PYTHON_EXECUTABLE=${PYTHON_EXECUTABLE}
408 -D PROJECT_VERSION=${GMX_VERSION_STRING}
409 -D PROJECT_SOURCE_DIR=${PROJECT_SOURCE_DIR}
410 -D DIRECTORIES_TO_CHECKSUM=${DIRECTORIES_TO_CHECKSUM_STRING}
411 -D VERSION_CMAKEIN=${VERSION_INFO_CMAKEIN_FILE_PARTIAL}
412 -D VERSION_OUT=${VERSION_INFO_CMAKE_FILE}
413 -D VERSION_STRING_OF_FORK=${GMX_VERSION_STRING_OF_FORK}
414 -P ${CMAKE_CURRENT_LIST_DIR}/gmxGenerateVersionInfoRelease.cmake
415 WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
416 COMMENT "Generating release version information")
417 list(APPEND VERSION_INFO_DEPS release-version-info)
419 configure_file(${VERSION_INFO_CMAKEIN_FILE}
420 ${VERSION_INFO_CMAKEIN_FILE_PARTIAL}
422 unset(GMX_VERSION_STRING_FULL)
423 unset(GMX_VERSION_FULL_HASH)
424 unset(GMX_VERSION_CENTRAL_BASE_HASH)
425 unset(GMX_RELEASE_SOURCE_FILE_CHECKSUM)
426 unset(GMX_CURRENT_SOURCE_FILE_CHECKSUM)
429 # What file the checksum should be written to
430 set(CHECKSUM_FILE "${PROJECT_SOURCE_DIR}/src/reference_checksum")
432 # Target that allows checksumming a source tree when producing a tarball.
433 # Allows verification of builds from the tarball to make sure the source had
434 # not been tampered with.
435 # Note: The RUN_ALWAYS here is to regenerate the hash file only, it does not
436 # mean that the target is run in all builds
437 if (PYTHONINTERP_FOUND)
438 # We need the full path to the directories after passing it through
439 set(FULL_PATH_DIRECTORIES "")
440 foreach(DIR ${SET_OF_DIRECTORIES_TO_CHECKSUM})
441 list(APPEND FULL_PATH_DIRECTORIES "${PROJECT_SOURCE_DIR}/${DIR}")
443 gmx_add_custom_output_target(reference_checksum RUN_ALWAYS
444 OUTPUT ${CHECKSUM_FILE}
445 COMMAND ${PYTHON_EXECUTABLE}
446 ${PROJECT_SOURCE_DIR}/admin/createFileHash.py
447 -s ${FULL_PATH_DIRECTORIES}
449 WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
450 COMMENT "Generating reference checksum of source files")
452 add_custom_target(reference_checksum
453 COMMAND ${CMAKE_COMMAND} -E echo
454 "Can not checksum files without python being available"
455 WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}
456 COMMENT "Generating reference checksum of source files")
459 # The main user-visible interface to the machinery.
460 # See documentation at the top of the script.
461 function (gmx_configure_version_file INFILE OUTFILE)
462 include(CMakeParseArguments)
463 set(_options REMOTE_HASH)
464 set(_one_value_args COMMENT TARGET)
465 set(_multi_value_args EXTRA_VARS)
466 cmake_parse_arguments(
467 ARG "${_options}" "${_one_value_args}" "${_multi_value_args}" ${ARGN})
468 if (ARG_UNPARSED_ARGUMENTS)
469 message(FATAL_ERROR "Unknown arguments: ${ARG_UNPARSED_ARGUMENTS}")
471 # Some callers may pass partial paths that do not really make sense,
472 # so create a default comment that only contains the actual file name.
473 get_filename_component(_basename ${OUTFILE} NAME)
474 set(_comment "Generating ${_basename}")
476 set(_comment ${ARG_COMMENT})
478 # Mimic configure_file()
479 if (NOT IS_ABSOLUTE ${INFILE})
480 set(INFILE ${CMAKE_CURRENT_SOURCE_DIR}/${INFILE})
482 # Create command-line definitions for the requested variables
483 set(_extra_var_defines)
484 foreach(_var ${ARG_EXTRA_VARS})
485 list(APPEND _extra_var_defines -D "${_var}=${${_var}}")
487 # The touch command is necessary to ensure that after the target is run,
488 # the timestamp is newer than in the input files.
489 add_custom_command(OUTPUT ${OUTFILE}
490 COMMAND ${CMAKE_COMMAND}
491 -D VERSION_VARIABLES=${VERSION_INFO_CMAKE_FILE}
492 -D VERSION_CMAKEIN=${INFILE}
493 -D VERSION_OUT=${OUTFILE}
494 ${_extra_var_defines}
495 -P ${VERSION_INFO_CONFIGURE_SCRIPT}
496 COMMAND ${CMAKE_COMMAND} -E touch ${OUTFILE}
497 WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
498 DEPENDS ${INFILE} ${VERSION_INFO_DEPS} ${VERSION_INFO_CONFIGURE_SCRIPT}
499 COMMENT "${_comment}"
502 add_custom_target(${ARG_TARGET} DEPENDS ${OUTFILE} VERBATIM)
503 gmx_set_custom_target_output(${ARG_TARGET} ${OUTFILE})