the default setup script name becomes "setup"
it can be changed in autocmake.cfg
This commit is contained in:
@ -8,7 +8,7 @@ solutions exist to this problem: GNU Makefiles is the traditional approach.
|
||||
Today, CMake is one of the trendier alternatives which can generate Makefiles
|
||||
starting from a file called ``CMakeLists.txt``.
|
||||
Autocmake composes CMake building blocks into a CMake project and generates
|
||||
``CMakeLists.txt`` as well as ``setup.py``, which serves as a front-end to
|
||||
``CMakeLists.txt`` as well as a setup script, which serves as a front-end to
|
||||
``CMakeLists.txt``. All this is done based on a lightweight ``autocmake.cfg``
|
||||
file::
|
||||
|
||||
@ -24,9 +24,9 @@ file::
|
||||
| python update.py .. |
|
||||
| |
|
||||
v v
|
||||
CMakeLists.txt (and setup.py front-end)
|
||||
CMakeLists.txt (and setup front-end)
|
||||
| |
|
||||
| python setup.py |
|
||||
| python setup |
|
||||
| which invokes CMake |
|
||||
v User of the code
|
||||
Makefile (or something else) |
|
||||
@ -44,7 +44,7 @@ scientific projects which typically have very similar requirements:
|
||||
|
||||
- Fortran and/or C and/or C++ support
|
||||
- Tuning of compiler flags
|
||||
- Front-end script with good defaults (setup.py)
|
||||
- Front-end script with good defaults
|
||||
- Support for parallelization: MPI, OMP, CUDA
|
||||
- Math libraries: BLAS, LAPACK
|
||||
|
||||
|
@ -7,9 +7,9 @@ Autocmake update and test scripts require Python 2.7 or higher. We try to also
|
||||
support Python 3 (tested with Python 3.4). If the script fails with Python 3,
|
||||
consider this a bug and please file an issue.
|
||||
|
||||
The generated ``setup.py`` runs with Python >= 2.7 (also tested with Python
|
||||
The generated setup script runs with Python >= 2.7 (also tested with Python
|
||||
3.4; probably also lower).
|
||||
|
||||
.. todo::
|
||||
|
||||
Figure out lower Python version bound for setup.py.
|
||||
Figure out lower Python version bound for setup.
|
||||
|
Reference in New Issue
Block a user