Merge tag 'v5.15.16-lts-lgpl' into 5.15

Qt 5.15.16-lts-lgpl release

.qmake.conf

@@ -1,3 +1,3 @@
 load(qt_build_config)
 
-MODULE_VERSION = 5.15.15
+MODULE_VERSION = 5.15.16

doc/src/development/moc.qdoc

@@ -44,10 +44,12 @@
     The C++ source file generated by \c moc must be compiled and
     linked with the implementation of the class.
 
-    If you use \l qmake to create your makefiles, build rules will be
+    Both \l qmake and \l {Build with CMake}{CMake} generate makefiles with
-    included that call the moc when required, so you will not need to
+    build rules that will invoke \c moc accordingly, so you will not need to use
-    use the moc directly. For more background information on \c moc,
+    the \c moc directly. \c qmake will add these build rules by default, whereas
-    see \l{Why Does Qt Use Moc for Signals and Slots?}
+    with CMake, you can use the \l {CMake AUTOMOC Documentation}{AUTOMOC}
+    property to handle \c moc automatically. For more background information on
+    \c moc, see \l{Why Does Qt Use Moc for Signals and Slots?}
 
     \section1 Usage
 
@@ -82,7 +84,9 @@
     will fail in the final link phase. If you use \c qmake, this is
     done automatically. Whenever \c qmake is run, it parses the
     project's header files and generates make rules to invoke \c moc
-    for those files that contain a Q_OBJECT macro.
+    for those files that contain a Q_OBJECT macro. Similarly, when setting
+    \l {CMake AUTOMOC Documentation}{AUTOMOC} to \c ON, CMake will scan the
+    header and source files at build time and invoke \c moc accordingly.
 
     If the class declaration is found in the file \c myclass.h, the
     moc output should be put in a file called \c moc_myclass.cpp.
@@ -98,9 +102,8 @@
     your program's makefile, \c make can take care of running moc
     when necessary and handling the moc output.
 
-    We recommend using the \l qmake makefile generation tool for
+    You can use \l {Build with CMake}{CMake} or \l qmake to generate makefiles
-    building your makefiles. This tool generates a makefile that does
+    that does all the necessary \c moc handling.
-    all the necessary \c moc handling.
 
     If you want to create your makefiles yourself, here are some tips
     on how to include moc handling.

doc/src/legal/licensechanges.qdoc

@@ -34,6 +34,36 @@
     Changes in Qt and \l{Licenses Used in Qt}{Third Party Modules}
     released with Qt that are relevant to licensing.
 
+    \section1 Qt 5.15.16
+
+    \section2 Qt Core Module
+
+    \list
+        \li The copy of the \l{psl}{Public Suffix List} was updated to
+        version 0522c13180d298cc10ac9d7e5a7d88aeb1856401, fetched on 2023-10-31.
+        \li \l{zlib}{Data Compression Library (zlib)} was updated to version
+        1.3.
+    \endlist
+
+    \section2 Qt GUI Module
+    \list
+        \li \l{harfbuzz}{HarfBuzz} was updated to upstream version 8.2.2.
+        \li \l{libjpeg}{LibJPEG-turbo} was updated to upstream version 3.0.1.
+        \li \l{freetype}{Freetype 2} was updated to upstream version 2.13.2.
+    \endlist
+
+    \section2 Qt Image Formats
+
+    \list
+        \li \l{libtiff}{TIFF Software Distribution (libtiff)} was updated to
+        upstream version 4.6.0.
+        \li {libwebp}{WebP (libwebp)} was updated to upstream version 1.3.2.
+    \endlist
+
+    \section2 Qt SQL Module
+
+    \l{sqlite}{SQLite} was updated to upstream version 3.43.2.
+
     \section1 Qt 5.15.15
 
     \section2 Qt Core Module

doc/src/platforms/emb-linux.qdoc

@@ -721,11 +721,11 @@
   help identifying the correct input device nodes and may uncover output
   configuration issues that can be difficult to debug otherwise.
 
-  \note As of Qt 5.8, the above is only supported for the evdevtouch input
+  \note As of Qt 5.14, the above is only supported for the evdevtouch and
-  backend. Other variants, such as the libinput-based one, will continue to
+  libinput backends. Other variants will continue to route events to the
-  route events to the primary screen. To force the usage of evdevtouch on
+  primary screen. To force the usage of evdevtouch on systems where multiple
-  systems where multiple input backends are available, set the environment
+  input backends are available, set the environment variable
-  variable \c QT_QPA_EGLFS_NO_LIBINPUT to \c 1.
+  \c QT_QPA_EGLFS_NO_LIBINPUT to \c 1.
 
   \section2 eglfs with other backends
 

examples/tutorials/alarms/main.cpp

@@ -57,7 +57,7 @@ int main(int argc, char *argv[])
     QGuiApplication app(argc, argv);
 
     QQmlApplicationEngine engine;
-    const QUrl url(u"qrc:/alarms/main.qml"_qs);
+    const QUrl url("qrc:/alarms/main.qml");
     QObject::connect(&engine, &QQmlApplicationEngine::objectCreated, &app,
                      [url](QObject *obj, const QUrl &objUrl) {
                          if (!obj && url == objUrl)