From d1baa79a05c9ff6ac958185688f19fb8369e9da8 Mon Sep 17 00:00:00 2001 From: Radovan Bast Date: Tue, 2 Jun 2015 21:49:40 +0200 Subject: [PATCH] formatting --- doc/about.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/about.rst b/doc/about.rst index 72e6de6..d23078b 100644 --- a/doc/about.rst +++ b/doc/about.rst @@ -3,7 +3,7 @@ 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. Autocmake assembles CMake modules, generates ``CMakeLists.txt`` as well as ``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 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 -maintaining the CMake infrastructure in many scientific projects which -typically have very similar requirements: +maintaining the CMake infrastructure in a growing number of scientific projects +which typically have very similar requirements: + - Fortran and/or C and/or C++ support - Compiler flags - Front-end script (setup.py) @@ -47,5 +48,6 @@ opportunity to introduce the occasional tweak without the need to read lengthy manuals. We try to follow two design principles: + - Explicit is better than implicit - Convention over configuration