QMake plugin should allow specifying custom Qt paths
Metadata
Current evaluation
The qmake plugin cannot build against Qt supplied by a part or local installation; the current craft-parts implementation hard-codes archive Qt packages and QT_SELECT. The valid feature remains unresolved.
Suggested action: keep open
Reason: Kalikiana clarified that applications must compile against Qt 5.8 headers supplied by a part, but craft-parts still installs only qt5-qmake or qmake6 and sets QT_SELECT to qt5 or qt6, with no custom-path property. The request remains valid but needs design work around part staging, SDK locations, and local installations; modern SDK build snaps may address some KDE Qt use cases but do not implement the requested plugin capability.
Evaluated by: mr-cal-bot
Impact:
48
Quick Win:
9
Complexity:
68
Confidence:
88
Actionability:
58
Issue body
Some projects require Qt versions higher than what Ubuntu offers in it's archives.
Thus it would be useful if the QMake plugin would support specifying Qt related paths to a custom Qt version.
Right now it is necessary to write your own plugin for this purpose as done in [1], [2].
I'm not sure how this should be implemented though. Simply using an environment variable like in [2]?
[1]: https://github.com/tjyrinki/timostestapp2
[2]: https://github.com/tim-sueberkrueb/liri-calculator-snap
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
9
Complexity:
68
Confidence:
88
Actionability:
58
|
keep open | The qmake plugin cannot build against Qt supplied by a part or local installation; the current craft-parts implementation hard-codes archive Qt packages and QT_SELECT. The valid feature remains unresolved. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
4
Complexity:
62
Confidence:
66
Actionability:
33
|
keep open | Feature request (2017, launchpad #1670146) for the qmake plugin to allow specifying custom Qt paths/versions, e.g. building against a Qt provided by a part or a local install instead of the archive Qt. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
14
Complexity:
50
Confidence:
75
Actionability:
70
|
needs triage | Feature request to allow specifying custom Qt paths in the QMake plugin. Unlabelled, no maintainer response, feature not yet implemented in craft-parts. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
15
Staleness:
95
Complexity:
40
Confidence:
55
Support Request:
20
|
close stale | Feature request to let the QMake plugin point at a custom Qt installation newer than Ubuntu's archives. Open ~9.5 years, zero comments, no labels, never triaged; the project later added the qbs plugin as the modern Qt build path. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
20
|
close stale | Feature request to allow custom Qt paths in the QMake plugin. Unlabeled, zero comments, and inactive for over nine years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
5
|
close stale | Feature request to allow custom Qt paths in the QMake plugin. Unlabelled, no maintainer response, and inactive for over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to allow custom Qt paths in the QMake plugin. Unaddressed for over 9 years with no maintainer comments or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #46 qml plugin: make it combinable with apps which use other build systems to install their files | snapcraft | closed | Feature request to make the qml plugin combinable with cmake-built parts was closed by maintainer in Nov 2015 as likely a part-ordering problem (cmake should run after qml); plugin was later deleted as broken. |