For compatibility reasons, this is only enabled when projects
upgrade their find_package(ECM) line to request a version >= 5.38.
A little bit like cmake policies: just upgrading ECM is compatible,
while increasing the required version can change behaviour.
Details
Details
Tested make test in all KF5 frameworks; I have patches
for some of them which I can't commit until this is in.
Diff Detail
Diff Detail
- Repository
- R240 Extra CMake Modules
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage
Comment Actions
Ooops, sorry. I had heavily tested ... a somewhat different version of the patch :(
Thanks for the fixes.
| kde-modules/KDECMakeSettings.cmake | ||
|---|---|---|
| 46–47 | Trying to fix things for kdevelop tests, I have to report that as user of ECM this note does not really assist me, besides hinting there is random magic happening :( So could you please add a comment telling what is that "layout" like, how does it help exactly running executables without installing? What other pre-conditions are need to be met? How should one rely on that layout in own cmake code? Commits like D7347 which make use of the here undocumented ${CMAKE_LIBRARY_OUTPUT_DIRECTORY} and then also point to yet another documentation source, on community.kde.org, instead of these docs, indicate things need some work here. | |
Comment Actions
Patch for more docu: https://phabricator.kde.org/D7612
BTW CMAKE_LIBRARY_OUTPUT_DIRECTORY is not undocumented, it's part of the cmake documentation:
Where to put all the :ref:`LIBRARY <Library Output Artifacts>` target files when built. This variable is used to initialize the ``LIBRARY_OUTPUT_DIRECTORY`` property on all the targets. See that target property for additional information.