aboutsummaryrefslogtreecommitdiff
path: root/find-modules/FindQtWaylandScanner.cmake
diff options
context:
space:
mode:
authorFriedrich W. H. Kossebau <kossebau@kde.org>2021-04-17 11:02:00 +0200
committerFriedrich W. H. Kossebau <kossebau@kde.org>2021-04-23 17:49:14 +0000
commit5512e03562694ebfe571a3b6068a7d35d9ddfd7a (patch)
tree3caca041d3526c8427ec3065642b41a52ad8578c /find-modules/FindQtWaylandScanner.cmake
parent38b5d046c4d42232d45bf4464167b2e6feea4cf7 (diff)
downloadextra-cmake-modules-5512e03562694ebfe571a3b6068a7d35d9ddfd7a.tar.gz
extra-cmake-modules-5512e03562694ebfe571a3b6068a7d35d9ddfd7a.tar.bz2
Modules docs: move rst docs into bracket comments
CMake >= 3.0 supports bracket comments, and the reStructuredText integration code in sphinx/ext/ecm.py already supports extracting the docs from a bracket comment instead. Editing documentation without leading line comment markers is more simple, e,g. when reflowing text over lines. With ECM meanwhile requiring CMake 3.5 now it is possible to switch (and thus follow also the approach used by cmake itself). NO_CHANGELOG
Diffstat (limited to 'find-modules/FindQtWaylandScanner.cmake')
-rw-r--r--find-modules/FindQtWaylandScanner.cmake123
1 files changed, 61 insertions, 62 deletions
diff --git a/find-modules/FindQtWaylandScanner.cmake b/find-modules/FindQtWaylandScanner.cmake
index efbbe87a..684ea8b8 100644
--- a/find-modules/FindQtWaylandScanner.cmake
+++ b/find-modules/FindQtWaylandScanner.cmake
@@ -1,68 +1,67 @@
-#.rst:
-# FindQtWaylandScanner
-# --------------------
-#
-# Try to find qtwaylandscanner.
-#
-# If the qtwaylandscanner executable is not in your PATH, you can provide
-# an alternative name or full path location with the ``QtWaylandScanner_EXECUTABLE``
-# variable.
-#
-# This will define the following variables:
-#
-# ``QtWaylandScanner_FOUND``
-# True if qtwaylandscanner is available
-#
-# ``QtWaylandScanner_EXECUTABLE``
-# The qtwaylandscanner executable.
-#
-# If ``QtWaylandScanner_FOUND`` is TRUE, it will also define the following imported
-# target:
-#
-# ``Wayland::QtScanner``
-# The qtwaylandscanner executable.
-#
-# This module provides the following functions to generate C++ protocol
-# implementations:
-#
-# - ``ecm_add_qtwayland_client_protocol``
-# - ``ecm_add_qtwayland_server_protocol``
-#
-# ::
-#
-# ecm_add_qtwayland_client_protocol(<source_files_var>
-# PROTOCOL <xmlfile>
-# BASENAME <basename>
-# [PREFIX <prefix>])
-#
-# Generate C++ wrapper to Wayland client protocol files from ``<xmlfile>``
-# XML definition for the ``<basename>`` interface and append those files
-# to ``<source_files_var>``. Pass the ``<prefix>`` argument if the interface
-# names don't start with ``qt_`` or ``wl_``.
-#
-# WaylandScanner is required and will be searched for.
-#
-# ::
-#
-# ecm_add_qtwayland_server_protocol(<source_files_var>
-# PROTOCOL <xmlfile>
-# BASENAME <basename>
-# [PREFIX <prefix>])
-#
-# Generate C++ wrapper to Wayland server protocol files from ``<xmlfile>``
-# XML definition for the ``<basename>`` interface and append those files
-# to ``<source_files_var>``. Pass the ``<prefix>`` argument if the interface
-# names don't start with ``qt_`` or ``wl_``.
-#
-# WaylandScanner is required and will be searched for.
-#
-# Since 1.4.0.
-
-#=============================================================================
# SPDX-FileCopyrightText: 2012-2014 Pier Luigi Fiorini <pierluigi.fiorini@gmail.com>
#
# SPDX-License-Identifier: BSD-3-Clause
-#=============================================================================
+
+#[=======================================================================[.rst:
+FindQtWaylandScanner
+--------------------
+
+Try to find qtwaylandscanner.
+
+If the qtwaylandscanner executable is not in your PATH, you can provide
+an alternative name or full path location with the ``QtWaylandScanner_EXECUTABLE``
+variable.
+
+This will define the following variables:
+
+``QtWaylandScanner_FOUND``
+ True if qtwaylandscanner is available
+
+``QtWaylandScanner_EXECUTABLE``
+ The qtwaylandscanner executable.
+
+If ``QtWaylandScanner_FOUND`` is TRUE, it will also define the following imported
+target:
+
+``Wayland::QtScanner``
+ The qtwaylandscanner executable.
+
+This module provides the following functions to generate C++ protocol
+implementations:
+
+ - ``ecm_add_qtwayland_client_protocol``
+ - ``ecm_add_qtwayland_server_protocol``
+
+::
+
+ ecm_add_qtwayland_client_protocol(<source_files_var>
+ PROTOCOL <xmlfile>
+ BASENAME <basename>
+ [PREFIX <prefix>])
+
+Generate C++ wrapper to Wayland client protocol files from ``<xmlfile>``
+XML definition for the ``<basename>`` interface and append those files
+to ``<source_files_var>``. Pass the ``<prefix>`` argument if the interface
+names don't start with ``qt_`` or ``wl_``.
+
+WaylandScanner is required and will be searched for.
+
+::
+
+ ecm_add_qtwayland_server_protocol(<source_files_var>
+ PROTOCOL <xmlfile>
+ BASENAME <basename>
+ [PREFIX <prefix>])
+
+Generate C++ wrapper to Wayland server protocol files from ``<xmlfile>``
+XML definition for the ``<basename>`` interface and append those files
+to ``<source_files_var>``. Pass the ``<prefix>`` argument if the interface
+names don't start with ``qt_`` or ``wl_``.
+
+WaylandScanner is required and will be searched for.
+
+Since 1.4.0.
+#]=======================================================================]
include(${CMAKE_CURRENT_LIST_DIR}/ECMFindModuleHelpersStub.cmake)
include("${ECM_MODULE_DIR}/ECMQueryQmake.cmake")