[qt/qt/qtgrpc]: Summary of bulk changes made

KDE Git Services - Bulk Change <[email protected]>
Newsgroups gmane.comp.kde.cvs
Message-ID <[email protected]>
Git repository change summary for qt/qt/qtgrpc
Pushed by mirror-service into branch '6.12'.
Changed from 3cf1dfd4d6b058c659ed32efb7a8dbd99bcc8d7d to 0b565970234b7cc0e2cfc170920ba00918767be5
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit f24e82bc1c0c7ee99f106eb1ca9632d512151f35 by Qt Submodule Update Bot on 13/08/2026 at 11:40..
Update dependencies on '6.12' in qt/qtgrpc

Change-Id: I5f722a2466d6fef4bc67962e923ffbe4bdfe506f
Reviewed-by: Qt Submodule Update Bot <[email protected]>
https://invent.kde.org/qt/qt/qtgrpc/-/commit/f24e82bc1c0c7ee99f106eb1ca9632d512151f35

Git commit 0b565970234b7cc0e2cfc170920ba00918767be5 by Qt Cherry-pick Bot (on behalf of Joerg Bornemann) on 13/08/2026 at 14:40..
CMake: Find ZLIB before gRPC in the standalone examples

...like we do with OpenSSL. And we already did the same fix for tests.

The standalone gRPC server examples find gRPC inside a block that sets
CMAKE_FIND_PACKAGE_PREFER_CONFIG to TRUE. gRPC's package config exports
gRPC::grpc with ZLIB::ZLIB in its link interface, but only resolves that
target itself via a guarded "if(NOT ZLIB_FOUND) find_package(ZLIB)".

Find ZLIB up front in MODULE mode, before enabling
CMAKE_FIND_PACKAGE_PREFER_CONFIG, so that ZLIB::ZLIB exists in the
consuming scope before gRPC is found. This mirrors the existing OpenSSL
handling and the same fix already done for the standalone tests.

Change-Id: I63f74abc0b1798ffd73181a7ad716415ce8c1bb6
Reviewed-by: Alexandru Croitor <[email protected]>
(cherry picked from commit 9126ca31e0b5c3bfd5f49df3aa720234a2964a0a)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
https://invent.kde.org/qt/qt/qtgrpc/-/commit/0b565970234b7cc0e2cfc170920ba00918767be5
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.