diff options
Diffstat (limited to 'Help/guide/tutorial')
| -rw-r--r-- | Help/guide/tutorial/Adding Usage Requirements for a Library.rst | 14 | ||||
| -rw-r--r-- | Help/guide/tutorial/Packaging Debug and Release.rst | 4 |
2 files changed, 11 insertions, 7 deletions
diff --git a/Help/guide/tutorial/Adding Usage Requirements for a Library.rst b/Help/guide/tutorial/Adding Usage Requirements for a Library.rst index aeb47c7..f9dc7cc 100644 --- a/Help/guide/tutorial/Adding Usage Requirements for a Library.rst +++ b/Help/guide/tutorial/Adding Usage Requirements for a Library.rst @@ -4,15 +4,20 @@ Step 3: Adding Usage Requirements for a Library Exercise 1 - Adding Usage Requirements for a Library ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Usage requirements allow for far better control over a library or -executable's link and include line while also giving more control over the -transitive property of targets inside CMake. The primary commands that +:ref:`Usage requirements <Target Usage Requirements>` of a target parameters +allow for far better control over a library or executable's link and include +line while also giving more control over the transitive property of targets +inside CMake. The primary commands that leverage usage requirements are: * :command:`target_compile_definitions` * :command:`target_compile_options` * :command:`target_include_directories` -* :command:`target_link_libraries` +* :command:`target_link_directories` +* :command:`target_link_options` +* :command:`target_precompile_headers` +* :command:`target_sources` + Goal ---- @@ -22,7 +27,6 @@ Add usage requirements for a library. Helpful Materials ----------------- -* :command:`target_include_directories` * :variable:`CMAKE_CURRENT_SOURCE_DIR` Files to Edit diff --git a/Help/guide/tutorial/Packaging Debug and Release.rst b/Help/guide/tutorial/Packaging Debug and Release.rst index e795be2..fc2050e 100644 --- a/Help/guide/tutorial/Packaging Debug and Release.rst +++ b/Help/guide/tutorial/Packaging Debug and Release.rst @@ -10,8 +10,8 @@ possible, however, to setup CPack to bundle multiple build directories and construct a package that contains multiple configurations of the same project. First, we want to ensure that the debug and release builds use different names -for the executables and libraries that will be installed. Let's use `d` as the -postfix for the debug executable and libraries. +for the libraries that will be installed. Let's use `d` as the +postfix for the debug libraries. Set :variable:`CMAKE_DEBUG_POSTFIX` near the beginning of the top-level ``CMakeLists.txt`` file: |