2 # This file is part of the GROMACS molecular simulation package.
4 # Copyright (c) 2019, by the GROMACS development team, led by
5 # Mark Abraham, David van der Spoel, Berk Hess, and Erik Lindahl,
6 # and including many others, as listed in the AUTHORS file in the
7 # top-level source directory and at http://www.gromacs.org.
9 # GROMACS is free software; you can redistribute it and/or
10 # modify it under the terms of the GNU Lesser General Public License
11 # as published by the Free Software Foundation; either version 2.1
12 # of the License, or (at your option) any later version.
14 # GROMACS is distributed in the hope that it will be useful,
15 # but WITHOUT ANY WARRANTY; without even the implied warranty of
16 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
17 # Lesser General Public License for more details.
19 # You should have received a copy of the GNU Lesser General Public
20 # License along with GROMACS; if not, see
21 # http://www.gnu.org/licenses, or write to the Free Software Foundation,
22 # Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
24 # If you want to redistribute modifications to GROMACS, please
25 # consider that scientific software is very special. Version
26 # control is crucial - bugs must be traceable. We will be happy to
27 # consider code for inclusion in the official distribution, but
28 # derived work must not be called official GROMACS. Details are found
29 # in the README & COPYING files - if they are missing, get the
30 # official version at http://www.gromacs.org.
32 # To help us fund GROMACS development, we humbly ask that you cite
33 # the research papers on the package. Check out http://www.gromacs.org.
35 # This CMakeLists.txt allows source distributions of the gmxapi Python package
36 # to rely on scikit-build for support of various Python packaging systems. The
37 # simplest use case is to allow the `setup.py` file to invoke skbuild to
38 # configure and run CMake. CMake could be invoked directly by the user or a
39 # parent package, but the Python distribution would not be packaged automatically.
40 # Reference https://redmine.gromacs.org/issues/2896 for additional discussion.
41 cmake_minimum_required(VERSION 3.9.6)
43 # This needs to be set before project() in order to pick up toolchain files
44 #list(APPEND CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR}/../../cmake)
46 # OS X deployment target should be >=10.9 for modern C++ compatibility.
47 # Reference https://scikit-build.readthedocs.io/en/latest/generators.html#macosx
48 # and https://github.com/MacPython/wiki/wiki/Spinning-wheels
49 set(CMAKE_OSX_DEPLOYMENT_TARGET 10.9 CACHE STRING
50 "OS X deployment target below 10.9 does not use modern standard library"
52 set(CMAKE_OSX_ARCHITECTURES x86_64 CACHE STRING
53 "OS X should build Python package for 64-bit architecture"
56 project(gmxapi VERSION 0.1.0)
58 # Check if Python package is being built directly or via add_subdirectory
59 set(GMXAPI_MASTER_PROJECT OFF)
60 if (CMAKE_CURRENT_SOURCE_DIR STREQUAL CMAKE_SOURCE_DIR)
61 set(GMXAPI_MASTER_PROJECT ON)
64 set(CMAKE_CXX_STANDARD 14)
65 set(CMAKE_CXX_STANDARD_REQUIRED ON)
67 # Only interpret if() arguments as variables or keywords when unquoted.
68 cmake_policy(SET CMP0054 NEW)
69 # honor the language standard settings for try_compile()
70 cmake_policy(SET CMP0067 NEW)
72 if(GMXAPI_MASTER_PROJECT)
73 find_package(gmxapi 0.0.8 REQUIRED
74 HINTS "$ENV{GROMACS_DIR}"
79 # GROMACS master branch and development branches may have divergent
80 # pre-release APIs. This check allows us to distinguish them and behave
81 # differently if needed. github.com/kassonlab/gromacs-gmxapi devel branch
82 # sets gmxapi_EXPERIMENTAL=TRUE. Upstream GROMACS master branch does not.
83 # Ref: https://github.com/kassonlab/gmxapi/issues/166
84 if(gmxapi_EXPERIMENTAL)
85 set(_suffix " (unofficial)")
87 message(STATUS "Found gmxapi version ${gmxapi_VERSION}${_suffix}")
90 set(GMXAPI_USE_BUNDLED_PYBIND ON CACHE BOOL
91 "Use pybind11 headers bundled with this repository. If OFF, CMake does `find_package(pybind11)`.")
92 if(GMXAPI_USE_BUNDLED_PYBIND)
93 add_subdirectory(external/pybind)
95 # Reference https://redmine.gromacs.org/issues/2896
96 find_package(pybind11 2.2 REQUIRED)
99 set(GMXAPI_PYTHON_EXTENSION_SOURCES
101 gmxapi/export_context.cpp
102 gmxapi/export_system.cpp
107 pybind11_add_module(_gmxapi
108 ${GMXAPI_PYTHON_EXTENSION_SOURCES}
111 target_include_directories(_gmxapi PRIVATE
112 ${CMAKE_CURRENT_SOURCE_DIR}/gmxapi
113 ${CMAKE_CURRENT_BINARY_DIR}/gmxapi
116 # RPATH management: make sure build artifacts can find GROMACS library.
117 set_target_properties(_gmxapi PROPERTIES SKIP_BUILD_RPATH FALSE)
118 set_target_properties(_gmxapi PROPERTIES BUILD_WITH_INSTALL_RPATH TRUE)
119 set_target_properties(_gmxapi PROPERTIES INSTALL_RPATH_USE_LINK_PATH TRUE)
121 # Python sources (*.py) will be packaged by scikit-build and setuptools.
122 # Library target will be build in CMAKE_LIBRARY_OUTPUT_DIRECTORY if not overridden.
123 # This may be an unexpected location whether inherited from the GROMACS build tree
124 # or the SKBUILD framework. When scikit-build is invoked with setup.py, the CMake
125 # build takes place in a subdirectory of ./_skbuild/.
126 set_target_properties(_gmxapi PROPERTIES LIBRARY_OUTPUT_DIRECTORY gmxapi_staging/gmxapi)
127 target_link_libraries(_gmxapi PRIVATE Gromacs::gmxapi)
129 # scikit-build sets SKBUILD when running Python packaging tools through setup.py
132 # By default, scikit-build expects the library to be installed into a directory
133 # named for the Python package as in setup.py.
134 install(TARGETS _gmxapi LIBRARY DESTINATION gmxapi)
136 # TODO: Determine packaging and installation cases and implementation.
137 # Reference https://redmine.gromacs.org/issues/2896 for additional discussion.
138 # Currently, CMake should be run by scikit-build through setup.py for proper Python packaging.
139 # We don't want to install by default in the outer scope of the GROMACS
140 # CMake procedure because we could end up trying to install to a system directory
141 # the user did not intend, or a user might install a Python-installation-specific
142 # package into an overly generic GROMACS path.
144 # Instead, we should probably build a source package and alert the user of its location.
145 # We can use CMake to call the Python packaging tools to create an 'sdist'
146 # source distribution archive to be installed in the GROMACS installation
147 # destination. We can use the build directory as the working directory for
148 # easier clean-up, as well.
149 # TODO: (ref issue #2896) Build and install 'sdist' with GROMACS.
151 # However, we can still produce an importable package for documentation builds and
152 # basic testing in ${CMAKE_CURRENT_BINARY_DIR}/gmxapi_staging
153 if(CMAKE_VERSION VERSION_LESS 3.12)
154 # CONFIGURE_DEPENDS appears in CMake 3.12 and can help to more robustly detect
155 # the need to update anything depending on the staged package.
156 file(GLOB_RECURSE _py_sources
158 ${CMAKE_CURRENT_SOURCE_DIR}/gmxapi/*.py)
160 file(GLOB_RECURSE _py_sources
161 ${CMAKE_CURRENT_SOURCE_DIR}/gmxapi/*.py)
163 foreach(_package_file IN LISTS _py_sources)
164 get_filename_component(_absolute_dir ${_package_file} DIRECTORY)
165 file(RELATIVE_PATH _relative_dir ${CMAKE_CURRENT_SOURCE_DIR} ${_absolute_dir})
166 file(COPY ${_package_file} DESTINATION gmxapi_staging/${_relative_dir})
168 file(COPY setup.py CMakeLists.txt DESTINATION gmxapi_staging)
169 # Set CMake variable pybind11_DIR to ${CMAKE_CURRENT_SOURCE_DIR}/external/pybind/tools
170 # if re-invoking CMake (including via Python setuptools) for the files in gmxapi_staging.
172 # Unit test and build docs using PYTHONPATH=$CMAKE_CURRENT_BINARY_DIR/gmxapi_staging/gmxapi
174 # Note: Integration testing for multiple Python versions and/or CMake-driven
175 # sdist preparation could be performed with CMake custom_commands and custom_targets.