Alexander Neundorf wrote: >> I do not understand why we can not install multiple versions of a library >> to one prefix. > > E.g. because we don't have versioned include dirs, so there can be only > one version in one prefix (talking about development installations).
Right, you were talking about development (with includes) installations. That answers a question I asked previously at least (when I mentioned -dev packages etc). > But, if you do > find_package(KCoreAddons NO_MODULE) > find_package(KArchive NO_MODULE) > find_package(KItemModules NO_MODULE) > you can do whatever you want. Ok, cool. I'm just wondering what restrictions are being imposed. We can have multiple layers of KDEDIRS env var, right? If you're restricting KDEFrameworksConfig.cmake to only two levels, that could have more consequences. >> >> Maybe there is a case for a cmake_maximum_version(). > Sure, but it it's easy to do, and doesn't require changes in cmake code > now and all the future (kind of backwards policy). Do you mean 'isn't' and 'does require...'? Yes, it's like a backwards policy. We would need to evaluate the effort of maintaining it, and more importantly Brad and David would have to agree and want it, because they would need to review all incoming patches for backwards policy compliance. I'll bring it to the CMake list. Thanks, Steve. _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
