[qt/qt/qtbase]: 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/qtbase Pushed by mirror-service into branch '6.11'. Changed from edaad186181e83bf196829632f2a6079148474ee to e30437a958a4adf98175a46cd23bcdb644ea959e 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 5af408c6d48b87c1ad86452aab0243be3c33f8df by Qt Cherry-pick Bot (on behalf of Laszlo Agocs) on 02/08/2026 at 02:45.. rhi autotest: Do not read back an uninitialized cubemap face renderToTextureCubemapFace reads back not only the face it renders into, but also another one, in order to verify that the layer parameter is not ignored. That face was never written to, and so the results of reading it back are undefined. With D3D12 it also makes the debug layer complain, because the subresources of a placed resource must be initialized with a Discard, Clear, or Copy operation before they can be used for anything else. Upload a known content to that face instead. This is a Copy, so it initializes the subresource, and it makes the readback result deterministic, which allows checking the uploaded color as well. Pick-to: 6.8 Change-Id: Ia0b5e21a3d57e3c598903242a77acb92736f2b70 Reviewed-by: Andy Nichols <[email protected]> (cherry picked from commit b96197efff3b5ac03d554df92c6fa444e64ef711) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit d17644917a00ef41dac1bed21eaeb65cd2bce01d) https://invent.kde.org/qt/qt/qtbase/-/commit/5af408c6d48b87c1ad86452aab0243be3c33f8df Git commit e30437a958a4adf98175a46cd23bcdb644ea959e by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 02/08/2026 at 02:45.. visionOS: Use the Swift driver to generate the bridging header We were invoking swiftc with -frontend, which bypasses the driver. The driver is what works out the macro plugin search paths for the target platform, passing -plugin-path, -external-plugin-path, and -in-process-plugin-server-path on to the frontend. Without them the frontend can't expand any Swift macros, which broke as of the Xcode 27 SDKs, where SwiftUI's @State is a macro rather than a property wrapper: error: external macro implementation type 'SwiftUIMacros.StateMacro' could not be found for macro 'State()'; plugin for module 'SwiftUIMacros' not found Passing the plugin paths ourselves is not much of an option, as SwiftUIMacros lives in the platform directory rather than the toolchain, so it needs the per-platform -external-plugin-path with the plugin server path appended. We let the driver work it out. Change-Id: I98ba5c3bc8d9a9d0ff8f4b0caf3a28f6e3e49090 Reviewed-by: Alexandru Croitor <[email protected]> (cherry picked from commit ebeca6b9490146c3f46b52b8a317f2d60ff8c595) Reviewed-by: Qt Cherry-pick Bot <[email protected]> (cherry picked from commit 3624cfe1a407e595cb973451f7a2bfbf03145219) https://invent.kde.org/qt/qt/qtbase/-/commit/e30437a958a4adf98175a46cd23bcdb644ea959e