diff --git a/Help/guide/tutorial/Getting Started with CMake.rst b/Help/guide/tutorial/Getting Started with CMake.rst index ae78dc6ae6..d72acb0281 100644 --- a/Help/guide/tutorial/Getting Started with CMake.rst +++ b/Help/guide/tutorial/Getting Started with CMake.rst @@ -337,7 +337,7 @@ To describe a collection of header files, we're going to use what's known as a library_implementation.cxx PUBLIC - FILE_SET MyHeaders + FILE_SET myHeaders TYPE HEADERS BASE_DIRS include @@ -525,19 +525,19 @@ Consider the following concrete example: target_sources(MyLibrary PRIVATE - FILE_SET InternalOnlyHeaders + FILE_SET internalOnlyHeaders TYPE HEADERS FILES InternalOnlyHeader.h INTERFACE - FILE_SET ConsumerOnlyHeaders + FILE_SET consumerOnlyHeaders TYPE HEADERS FILES ConsumerOnlyHeader.h PUBLIC - FILE_SET PublicHeaders + FILE_SET publicHeaders TYPE HEADERS FILES PublicHeader.h @@ -554,9 +554,9 @@ Two specific properties which will be modified here are :prop_tgt:`HEADER_SETS` and :prop_tgt:`INTERFACE_HEADER_SETS`, which both contain lists of header file sets added via :command:`target_sources`. -The value ``InternalOnlyHeaders`` will be added to :prop_tgt:`HEADER_SETS`, -``ConsumerOnlyHeaders`` to :prop_tgt:`INTERFACE_HEADER_SETS`, and -``PublicHeaders`` will be added to both. +The value ``internalOnlyHeaders`` will be added to :prop_tgt:`HEADER_SETS`, +``consumerOnlyHeaders`` to :prop_tgt:`INTERFACE_HEADER_SETS`, and +``publicHeaders`` will be added to both. When a given target is being built, it will use its own *non-interface* properties (eg, :prop_tgt:`HEADER_SETS`), combined with the *interface* diff --git a/Help/guide/tutorial/Installation Commands and Concepts.rst b/Help/guide/tutorial/Installation Commands and Concepts.rst index b281385a1f..c2422a5865 100644 --- a/Help/guide/tutorial/Installation Commands and Concepts.rst +++ b/Help/guide/tutorial/Installation Commands and Concepts.rst @@ -101,13 +101,13 @@ and consists of a single call to :command:`install(targets)`. TARGETS MyApp MyLib FILE_SET HEADERS - FILE_SET AnotherHeaderFileSet + FILE_SET anotherHeaderFileSet ) Most artifact kinds are installed by default and do not need to be listed in the :command:`install` command. However, ``FILE_SET``\ s must be named to let CMake know you want to install. In the above example we install two file -sets, one named ``HEADERS`` and another named ``AnotherHeaderFileSet``. +sets, one named ``HEADERS`` and another named ``anotherHeaderFileSet``. When named, an artifact kind can be given various options, such as a destination.