This is primarily useful for cross-compilation, where e.g. with Yocto
neither Qt5Widgets nor PolicyKit are easily available for the host build.
Details
Details
- Reviewers
cordlandwehr apol - Group Reviewers
Frameworks - Maniphest Tasks
- T6716: Fix native kauth-policy-gen build for KAuth
- Commits
- R283:af4f0052f1ef: Allow to only build the kauth-policy-gen code generator
Diff Detail
Diff Detail
- Repository
- R283 KAuth
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
| CMakeLists.txt | ||
|---|---|---|
| 91 | This installs KF5AuthTargets.cmake based on the condition, but KF5AuthConfig.cmake still includes the target file unconditionally, so cmake would fail over missing the file when using find_package(KF5Auth). So are the cmake files not used in the case to support here at all, and all of the cmake config handling should be wrapped? | |
| CMakeLists.txt | ||
|---|---|---|
| 91 | Right, the config files don't need to be installed in this case either. This was done for cross-compilation, nothing on the host system will use KAuth via a CMake config file. We do need the tools targets config file though, but that is separate. | |