aboutsummaryrefslogtreecommitdiff
path: root/modules
diff options
context:
space:
mode:
authorFriedrich W. H. Kossebau <kossebau@kde.org>2018-03-18 18:06:44 +0100
committerFriedrich W. H. Kossebau <kossebau@kde.org>2018-03-18 18:06:44 +0100
commite75d9234b96aca7edbc828c64d98ac4fd177a520 (patch)
tree29cce7f14c62f10c76953298efcdecba11b6a752 /modules
parent36d42640576e92f8ddb3a66d35738f8fe75d1b8c (diff)
downloadextra-cmake-modules-e75d9234b96aca7edbc828c64d98ac4fd177a520.tar.gz
extra-cmake-modules-e75d9234b96aca7edbc828c64d98ac4fd177a520.tar.bz2
API dox: fix some "code-block" lines to have empty lines before/after
Diffstat (limited to 'modules')
-rw-r--r--modules/ECMSetupQtPluginMacroNames.cmake5
1 files changed, 5 insertions, 0 deletions
diff --git a/modules/ECMSetupQtPluginMacroNames.cmake b/modules/ECMSetupQtPluginMacroNames.cmake
index 13df687f..1380250f 100644
--- a/modules/ECMSetupQtPluginMacroNames.cmake
+++ b/modules/ECMSetupQtPluginMacroNames.cmake
@@ -43,7 +43,9 @@
#
# Given some plugin-oriented Qt-based software which defines a custom C++ preprocessor
# macro ``EXPORT_MYPLUGIN`` for declaring the central plugin object:
+#
# .. code-block:: c++
+#
# #define EXPORT_MYPLUGIN_WITH_JSON(classname, jsonFile) \
# class classname : public QObject \
# { \
@@ -53,6 +55,7 @@
# };
#
# In the CMake buildsystem of the library one calls
+#
# .. code-block:: cmake
#
# ecm_setup_qtplugin_macro_names(
@@ -68,6 +71,7 @@
# plugins by linking against the library, one passes additionally the name of
# a variable which shall be set as value the CMake code needed to instruct
# automoc about the usage of that macro.
+#
# .. code-block:: cmake
#
# ecm_setup_qtplugin_macro_names(
@@ -81,6 +85,7 @@
# ``MyProjectConfig.cmake.in``) for the libary's installed CMake config file
# and that way will ensure that in the 3rd-party plugin's buildsystem
# automoc is instructed as well as needed:
+#
# .. code-block:: cmake
#
# @PACKAGE_SETUP_AUTOMOC_VARIABLES@