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

When using the Emscripten toolchain, there is no library linkage
necessary (there is no library) and the system include search paths
provide EGL headers.

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D24182

Summary:
${EGL_INCLUDE_DIR} is the path up to 'egl.h' -- so the header is
${EGL_INCLUDE_DIR}/egl.h

The compile test on the other hand includes 'EGL/egl.h', so the path
that needs to be passed to the compile test is "${EGL_INCLUDE_DIR}/..".

Reviewers: #automotive, hausmann, #freebsd, apol

Reviewed By: #automotive, hausmann, apol

Subscribers: bcooksley, kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D19075

Perform additional sanity checking by doing a compile test.

Differential Revision: https://phabricator.kde.org/D18960

REVIEW: 123470

There is no "\t" in CMake's regular expression syntax; we need to make
the character be interpreted when CMake parses it as a string.