generated from ENCCS/sphinx-lesson-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
39682dd
commit 8d216e0
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
.. _tips-and-tricks: | ||
|
||
|
||
Tips and tricks using CMake | ||
============================ | ||
|
||
|
||
.. objectives:: | ||
|
||
- Learn what tools exist to structure projects as they grow. | ||
- Discuss the value of localizing scope and avoiding side effects. | ||
- Recognize more maintainable and less maintainable patterns. | ||
|
||
|
||
As projects grow, code structures get more complicated: more possibilities, more corner cases, more options to users, and more developers who are contributing and may not oversee the entire CMake structure. In this episode we will mention a couple of tools to bring some structure and flow-control into larger projects. [#adapt_from_CR]_ | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
.. rubric:: Footnotes | ||
|
||
.. [#adapt_from_CR] This episode is adapted, with permission, from the `CodeRefinery CMake lesson <https://coderefinery.github.io/cmake-workshop/growing-projects>`_. | ||