1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: Add "since"-note about 6.8 additions in cmake API

Browse Source 
The PUBLIC_CODE/PRIVATE_CODE APIs were added to the cmake
functions in Qt 6.8, so this should be mentioned in the docs.

Pick-to: 6.8
Change-Id: I0430cbc659ddd2db65401b94811ca0d4c8f12010
Reviewed-by: David Redondo <qt@david-redondo.de>
This commit is contained in:
Eskil Abrahamsen Blomfeldt 2024-08-15 08:24:42 +02:00
parent af6f515806
commit 458aadde42
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/plugins/platforms/wayland/doc/src/cmake/qt_generate_wayland_protocol_client_sources.qdoc
View File

@ -36,8 +36,8 @@ qt_generate_wayland_protocol_client_sources() creates the build steps to run \c{
code in C and C++ for implementing the protocols, and the resulting files will be built as part
of the \c target.
The options \c{PUBLIC_CODE} and \c{PRIVATE_CODE} correspond to the \c{public-code} and
\c{private-code} options of \c{wayland-scanner}. \c{PUBLIC_CODE} will cause the symbols in the
The options \c{PUBLIC_CODE} and \c{PRIVATE_CODE} (added in Qt 6.8) correspond to the \c{public-code}
and \c{private-code} options of \c{wayland-scanner}. \c{PUBLIC_CODE} will cause the symbols in the
code that is generated by \c{wayland-scanner} to be exported. For backwards compatibility \c{PUBLIC_CODE} is the
default but generally \c{PRIVATE_CODE} is strongly recommended.