summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2014-02-05 14:34:27 (GMT)
committerCMake Topic Stage <kwrobot@kitware.com>2014-02-05 14:34:27 (GMT)
commitc475b42a66ba5a35e7a84273aca118d5037dd54d (patch)
tree5c383003dadd17b199621255f9ef96c89de86dda
parent43a78f5b295fb68012e41ebe32b8d78fca63261f (diff)
parent635e96dde29e7f76e66870dbebfc332360e1ddca (diff)
downloadCMake-c475b42a66ba5a35e7a84273aca118d5037dd54d.zip
CMake-c475b42a66ba5a35e7a84273aca118d5037dd54d.tar.gz
CMake-c475b42a66ba5a35e7a84273aca118d5037dd54d.tar.bz2
Merge topic 'AUTOMOC-docs'
635e96dd Help: Be clearer about which header files are considered for AUTOMOC
-rw-r--r--Help/prop_tgt/AUTOMOC.rst7
1 files changed, 5 insertions, 2 deletions
diff --git a/Help/prop_tgt/AUTOMOC.rst b/Help/prop_tgt/AUTOMOC.rst
index 16094c7..5e07063 100644
--- a/Help/prop_tgt/AUTOMOC.rst
+++ b/Help/prop_tgt/AUTOMOC.rst
@@ -12,8 +12,11 @@ statement like ``#include "moc_foo.cpp"`` is found, the ``Q_OBJECT`` class
declaration is expected in the header, and ``moc`` is run on the header
file. If an ``#include`` statement like ``#include "foo.moc"`` is found, then
a ``Q_OBJECT`` is expected in the current source file and ``moc`` is run on
-the file itself. Additionally, all header files are parsed for
-``Q_OBJECT`` macros, and if found, ``moc`` is also executed on those files.
+the file itself. Additionally, header files with the same base name (like
+``foo.h``) or ``_p`` appended to the base name (like ``foo_p.h``) are parsed
+for ``Q_OBJECT`` macros, and if found, ``moc`` is also executed on those files.
+``AUTOMOC`` checks multiple header alternative extensions, such as
+``hpp``, ``hxx`` etc when searching for headers.
The resulting moc files, which are not included as shown above in any
of the source files are included in a generated
``<targetname>_automoc.cpp`` file, which is compiled as part of the