AnotherFoxGuy/autocmake
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

formatting

Browse Source
This commit is contained in:
Radovan Bast
2015-06-02 21:49:40 +02:00
parent 02b848be77
commit d1baa79a05
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/about.rst
View File

@ -3,7 +3,7 @@
About Autocmake About Autocmake
=============== ===============
You typically want to use CMake when you are tired of manually editing You typically want to use CMake when you get tired of manually editing
Makefiles. Autocmake is for people who are tired of editing CMake files. Makefiles. Autocmake is for people who are tired of editing CMake files.
Autocmake assembles CMake modules, generates ``CMakeLists.txt`` as well as Autocmake assembles CMake modules, generates ``CMakeLists.txt`` as well as
``setup.py``, which serves as a front-end to ``CMakeLists.txt``. All this is ``setup.py``, which serves as a front-end to ``CMakeLists.txt``. All this is
@ -30,8 +30,9 @@ Why Autocmake
The main motivation for us to create Autocmake as a CMake framework library was The main motivation for us to create Autocmake as a CMake framework library was
to simplify CMake code transfer between codes. We got tired of manually diffing to simplify CMake code transfer between codes. We got tired of manually diffing
and and copy-pasting boiler-plate CMake code and watching it diverge while and and copy-pasting boiler-plate CMake code and watching it diverge while
maintaining the CMake infrastructure in many scientific projects which maintaining the CMake infrastructure in a growing number of scientific projects
typically have very similar requirements: which typically have very similar requirements:
- Fortran and/or C and/or C++ support - Fortran and/or C and/or C++ support
- Compiler flags - Compiler flags
- Front-end script (setup.py) - Front-end script (setup.py)
@ -47,5 +48,6 @@ opportunity to introduce the occasional tweak without the need to read lengthy
manuals. manuals.
We try to follow two design principles: We try to follow two design principles:
- Explicit is better than implicit - Explicit is better than implicit
- Convention over configuration - Convention over configuration