update doc
This commit is contained in:
parent
f9b0527738
commit
ede53a5803
@ -11,7 +11,7 @@ Directly inside the generated modules directory
|
||||
|
||||
The CMake modules can be customized directly inside ``modules/`` but this is
|
||||
the least elegant solution since the customizations may be overwritten by the
|
||||
``boostrap.py`` script.
|
||||
``boostrap.py`` script (use version control).
|
||||
|
||||
|
||||
Adapt local copies of CMake modules
|
||||
@ -19,14 +19,14 @@ Adapt local copies of CMake modules
|
||||
|
||||
A better solution is to download the CMake modules that you wish you customize
|
||||
to a separate directory and source the customized CMake modules in
|
||||
``autocmake.cfg``.
|
||||
``autocmake.cfg``. Alternatively you can serve your custom
|
||||
modules from your own http server.
|
||||
|
||||
|
||||
Create own CMake modules
|
||||
------------------------
|
||||
|
||||
Of course you can also create own modules and source them in ``autocmake.cfg``.
|
||||
Sometimes you have to.
|
||||
|
||||
|
||||
Contribute customizations to the "standard library"
|
||||
@ -35,4 +35,4 @@ Contribute customizations to the "standard library"
|
||||
If you think that your customization will be useful for other users as well,
|
||||
you may consider contributing the changes directly to
|
||||
https://github.com/scisoft/autocmake/. We very much encourage such
|
||||
contributions. But we of course also strive for generality and portability.
|
||||
contributions. But we also very much strive for generality and portability.
|
||||
|
Loading…
x
Reference in New Issue
Block a user