Bug 419476 - snap sdk: KF5 qmake modules have non-configurable paths in their .pri files
Summary: snap sdk: KF5 qmake modules have non-configurable paths in their .pri files
Status: REPORTED
Alias: None
Product: neon
Classification: KDE Neon
Component: Snaps (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Scarlett Moore
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-01 09:05 UTC by Maximilian Federle
Modified: 2022-10-18 15:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maximilian Federle 2020-04-01 09:05:17 UTC 
# 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