0.15.2: Qt at its upstream version, 6.11.1; a synthesised rules-qt program that was asked for nothing reports nothing - #34
Merged
Conversation
…ogram that was asked for nothing reports nothing - The fixtures, the missing-SDK message and docs/rules-qt.md name xim:qt-base and xim:qt 6.11.1, the single key the index keeps (openxlings/xim-pkgindex#891). - docs/rules-qt.md states how a project uses its own Qt: comment out the declared payload, then name the SDK with QT_ROOT_DIR or options::root. - A package that enables rules-qt only to import mcpp.rules.qt and writes no build.mcpp runs the program mcpp synthesises (mcpp#715). With no SDK and no .ui, .qrc or .ts of its own it now says nothing; the qt-import-only fixture holds that. - The CI sandbox caches take a new generation, so none restores the Qt payload laid out before the runtime closure.
…3 does not (mcpp#713), the warnings came from gpp.build's synthesised program (mcpp#715)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
xim:qt-baseandxim:qtare named at6.11.1in the fixtures, in the missing-SDK message and indocs/rules-qt.md. The index keeps one key per Qt package (qt, qt-base, qt-addons: one key, 6.11.1, with the runtime closure; brotli's assets under their canonical names openxlings/xim-pkgindex#891). The package has had no consumers beyond CI, so the correction to its layout (the runtime closure) stays under the upstream version and does not need the revision key6.11.1.1.docs/rules-qt.mdsays how to use one: comment out the declared payload, becausemcpp buildprovisions every declared payload, then name the SDK withQT_ROOT_DIRor withoptions::rootinbuild.mcpp.rules-qtonly to importmcpp.rules.qt, such as GalTranslPP'sgpp.build, has nobuild.mcpp, so it runs the program that mcpp synthesises (mcpp#715). Such a package also has no SDK and no.ui,.qrcor.ts. The program now reports nothing; it used to print "no Qt SDK", 5 times per GalTranslPPemit. A package with its ownbuild.mcpp, or with Qt device sources, still gets the report. The new fixturetests/qt-import-onlyholds this on all three platforms.mcpp-sandbox-v2-…), so no job restores a Qt payload laid out before the runtime closure.Verification (local, Linux, gcc 16.1.0, mcpp 2026.9.26.2)
Before these checks, the sandbox's Qt payloads and their provisioning stamps were removed, so each check installs
6.11.1fresh. Removing the stamps was necessary because of mcpp#716.QT_ROOT_DIR, thenoptions::root.6.11.1is the corrected payload.