Where to put KDE Frameworks cmake stuff...

[Stephen Kelly]

Alexander Neundorf wrote:
> I thought more about it.
> How about that:
> 
> find_package(KF5 COMPONENTS kcore kwidgets kitemmodels)
> 
> searches in the normal cmake way for kcoreConfig.cmake, using
> CMAKE_PREFIX_PATH and all that. Additionally automatically also using
> KDEDIRS.
> 
> Once it has found the first requested component, the remaining components
> are searched first in the same prefix as the first one, and after that in
> KDEDIRS, and in no other directories, no CMAKE_PREFIX_PATH etc.
> 
> This way, without having KDEDIRS set, libraries from KDE frameworks will
> all be found in the same prefix.
> If you want to search in multiple directories, you can adjust the KDEDIRS
> environment variable.

It seems odd that for any project except KDE, you set CMAKE_PREFIX_PATH and 
for KDE you have to set KDEDIRS instead. You're removing and re-adding the 
feature with a different name. 

If the shared-install-dirs is removed, is the SHADOWING feature you 
mentioned before needed anymore?


> Now that it seems the shared-install-dirs feature can be removed, this
> could be good enough.
> It would imply that e-c-m will be updated relatively often 

Why would it need to be updated relatively often? Why does the removal of 
the shared-install-dirs feature imply that?

> and that the
> kde-modules/ dir in e-c-m will indeed be quite KDE-ish.

So, are you dropping the idea of a separate dependency which everything 
depends on?

Thanks,

Steve.