| Summary: | snap sdk: KF5 qmake modules have non-configurable paths in their .pri files | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Maximilian Federle <max.federle> |
| Component: | Snaps | Assignee: | Scarlett Moore <sgmoore> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | neon-bugs-null, sgmoore |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
# Applies to kde-frameworks-5-core18-sdk kde-frameworks-5-qt-5-14-core18-sdk # Summary KF5 modules have .pri files with absolute and unconfigurable paths in them: E.g. ``` cat ./usr/lib/x86_64-linux-gnu/qt5/mkspecs/modules/qt_KAuth.pri [...] QT.KAuth.includes = /usr/include/KF5/KAuth QT.KAuth.private_includes = QT.KAuth.libs = /usr/lib/x86_64-linux-gnu [...] ``` The corresponding cmake files respect _IMPORT_PREFIX. The Qt modules do also respect $$QT_MODULE_INCLUDE_BASE in their .pri files # Problem With the sdk snaps being used as build snaps, they are not mounted at /, but at /snap/${SNAP_NAME} and thus those absolute paths are invalid when using qmake. # Expectation KF5 modules include a prefix variable like their Qt companions. As a consequence, they respect Prefix set in qt.conf