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 # Python setuptools script to build and install the gmxapi Python interface
36 # from a GROMACS installation directory.
38 # Usage note: things go smoothly when we stick to the setup.py convention of
39 # having a package source directory with the same name as the package at the
40 # same level as the setup.py script and only expect `pip install .` in the
41 # setup.py directory. If we play with the layout more, it is hard to keep all
42 # of the `pip` and `setup.py` cases working as expected. This is annoying
43 # because running the Python interpreter immediately from the same directory
44 # can find the uninstalled source instead of the installed package. We can
45 # ease this pain by building an sdist in the enclosing CMake build scope
46 # and encouraging users to `pip install the_sdist.archive`. Otherwise, we
47 # just have to document that we only support full build-install of the Python
48 # package from the directory containing setup.py, which may clutter that
49 # directory with some artifacts.
51 from skbuild
import setup
56 # TODO: (pending infrastructure and further discussion) Replace with CMake variables from GMXAPI version.
58 python_requires
='>=3.4, <4',
59 setup_requires
=['setuptools>=28'],
62 cmake_args
=['-DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=10.9',
63 '-DCMAKE_OSX_ARCHITECTURES:STRING=x86_64'],
65 author
='M. Eric Irrgang',
66 author_email
='info@gmxapi.org',
67 description
='gmxapi Python interface for GROMACS',
69 url
='http://gmxapi.org/',
71 # The installed package will contain compiled C++ extensions that cannot be loaded
72 # directly from a zip file.