https://bugs.kde.org/show_bug.cgi?id=419476
Bug ID: 419476
Summary: snap sdk: KF5 qmake modules have non-configurable
paths in their .pri files
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Snaps
Assignee: neon-b...@kde.org
Reporter: max.fede...@googlemail.com
CC: neon-b...@kde.org
Target Milestone: ---
# 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
--
You are receiving this mail because:
You are watching all bug changes.
