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

more doc

Browse Source
This commit is contained in:
Radovan Bast 2015-08-02 12:46:36 +02:00
parent 2ec27da616
commit b30bfa3e01
2 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/developers/example.rst
View File

@ -141,7 +141,8 @@ Now we are ready to build::
[100%] Linking Fortran executable hello.x [100%] Linking Fortran executable hello.x
[100%] Built target hello.x [100%] Built target hello.x
Excellent! All that could have been done with few command lines directly but Excellent! But this was a lot of typing and file creating just to get a simple
now we have a cross-platform project and can extend it and customize it and we executable compiled!? Of course, all that could have been done with few command
got a front-end script and command-line parser for free. Now go out and lines directly but now we have a cross-platform project and can extend it and
explore more Autocmake modules and features. customize it and we got a front-end script and command-line parser for free.
Now go out and explore more Autocmake modules and features.

8
doc/developers/faq.rst
View File

@ -68,7 +68,7 @@ Autocmake does not do feature X - I really need feature X and a setup.py flag --
The Autocmake developers have to be very conservative and only a very limited The Autocmake developers have to be very conservative and only a very limited
set of portable features of absolutely general interest become part of the set of portable features of absolutely general interest become part of the
Autocmake core or an Autocmake module. Autocmake core or an Autocmake module. Autocmake developers are also busy.
Our recommendation is to not wait for the feature to be implemented: Implement Our recommendation is to not wait for the feature to be implemented: Implement
it yourself. Here we show you how. Code your feature in a module (i.e. it yourself. Here we show you how. Code your feature in a module (i.e.
@ -91,6 +91,6 @@ want a ``setup.py`` flag to toggle the feature::
docopt: --my-feature Enable my feature [default: False]. docopt: --my-feature Enable my feature [default: False].
define: '-DENABLE_MY_FEATURE=%s' % arguments['--my-feature'] define: '-DENABLE_MY_FEATURE=%s' % arguments['--my-feature']
Implement your ideas, test them, and share them. If your module is portable Implement your ideas, test them, and share them. If your module is portable,
and of general interest, you can suggest it to be part of the standard set of good code quality, and of general interest, you can suggest it to be part of
modules or even a core feature. the standard set of modules or even a core feature.