summaryrefslogtreecommitdiffstats
path: root/Help/manual
diff options
context:
space:
mode:
authorSebastian Holtermann <sebholt@xwmw.org>2017-09-25 17:52:11 (GMT)
committerSebastian Holtermann <sebholt@xwmw.org>2017-09-28 07:21:44 (GMT)
commit08041dd15e7a4a030b2458e70018b50e1bbc0939 (patch)
tree89388697991b94120652300ac5ec648ea869506c /Help/manual
parent7b33d67bc53446e89eb27d750d80e4b639f8d3e5 (diff)
downloadCMake-08041dd15e7a4a030b2458e70018b50e1bbc0939.zip
CMake-08041dd15e7a4a030b2458e70018b50e1bbc0939.tar.gz
CMake-08041dd15e7a4a030b2458e70018b50e1bbc0939.tar.bz2
Autogen: Doc: Update documentation for (CMAKE_)AUTOMOC_MACRO_NAMES
Diffstat (limited to 'Help/manual')
-rw-r--r--Help/manual/cmake-qt.7.rst11
1 files changed, 5 insertions, 6 deletions
diff --git a/Help/manual/cmake-qt.7.rst b/Help/manual/cmake-qt.7.rst
index 79e7e79..cafeae1 100644
--- a/Help/manual/cmake-qt.7.rst
+++ b/Help/manual/cmake-qt.7.rst
@@ -59,9 +59,10 @@ The :prop_tgt:`AUTOMOC` target property controls whether :manual:`cmake(1)`
inspects the C++ files in the target to determine if they require ``moc`` to
be run, and to create rules to execute ``moc`` at the appropriate time.
-If a ``Q_OBJECT`` or ``Q_GADGET`` macro is found in a header file, ``moc``
-will be run on the file. The result will be put into a file named according
-to ``moc_<basename>.cpp``. If the macro is found in a C++ implementation
+If a macro from :prop_tgt:`AUTOMOC_MACRO_NAMES` is found in a header file,
+``moc`` will be run on the file. The result will be put into a file named
+according to ``moc_<basename>.cpp``.
+If the macro is found in a C++ implementation
file, the moc output will be put into a file named according to
``<basename>.moc``, following the Qt conventions. The ``<basename>.moc`` must
be included by the user in the C++ implementation file with a preprocessor
@@ -95,9 +96,7 @@ following targets by setting the :variable:`CMAKE_AUTOMOC` variable. The
options to pass to ``moc``. The :variable:`CMAKE_AUTOMOC_MOC_OPTIONS`
variable may be populated to pre-set the options for all following targets.
-The appearance of the strings ``Q_OBJECT`` or ``Q_GADGET`` in a source file
-determines if it needs to be ``moc`` processed. To search for additional
-strings, list them in :prop_tgt:`AUTOMOC_MACRO_NAMES`.
+Additional macro names to search for can be added to :prop_tgt:`AUTOMOC_MACRO_NAMES`.
Additional ``moc`` dependency file names can be extracted from source code
by using :prop_tgt:`AUTOMOC_DEPEND_FILTERS`.