Skip to content

Grammar/Flow #475

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rbsheth merged 2 commits into from
Oct 13, 2021
Merged

Grammar/Flow #475

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e1b0d7b
Grammar/Flow
Leviathes Oct 11, 2021
4a921a0
Update cmake-user.rst
Leviathes Oct 13, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions docs/user-guides/cmake-user.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,19 +5,20 @@ CMake user
----------

This kind of developer can **read** CMake code that was written by more
experienced CMake developer. He understand some simple features like that
executable added by ``add_executable`` command and this command contains list
of sources files. But probably will not be able to tell why in some cases
``include_directories`` command called but ``target_include_directories`` in
other cases. The main target of modifications is C++ code.
experienced CMake developers. They understand some simple features such as
adding an executable with the ``add_executable`` command, and that this
command contains a list of source files associated with the executable.
They will probably have difficulty understanding why, in some cases, the
``include_directories`` command is called, but in others, ``target_include_directories``
is called instead. The main target of modifications is C++ code.

Such developers can do:
Such developers can:

* Add more targets to project
* Add more targets to projects
* Add more sources to targets
* Add C++ flags that does not break compatibility (e.g. warnings/optimization)
* Add C++ flags that don't break compatibility (e.g. warnings/optimization)

Such developers can't do:
Such developers can't:

* Add more external dependencies to project
* Adding flags that can break compatibility (e.g. ``-std=c++11`` or ``/MT``)
Expand Down