changes to how kdepimlibs and kdebase/workspace are installed and found
neundorf at kde.org
Thu Dec 18 19:31:00 CET 2008
On Thursday 18 December 2008, Brad King wrote:
> Alexander Neundorf wrote:
> > On Tuesday 09 December 2008, Brad King wrote:
> >> Brad King wrote:
> >>> Brad King wrote:
> >>>> Perhaps you can avoid this by using PATH_SUFFIXES on the inner
> >>>> find_package call in your find-modules:
> >>>> find_package(KFoo NO_MODULE PATH_SUFFIXES cmake)
> >>>> Then you can just always install to cmake/kfoo. Once a version of
> >>>> CMake supporting this location is required in the future this suffix
> >>>> can be removed.
> >>> Oops, nevermind. The PATH_SUFFIXES get appended to each generated
> >>> path, not to each prefix.
> >> I think you'll just have to require 2.6.3 if you want to move the files
> >> from kfoo/cmake to cmake/kfoo.
> > No chance, it's not released yet, and people just complained enough that
> > we required 2.6.2, and we are about to freeze:
> > http://techbase.kde.org/Schedules/KDE4/4.2_Release_Schedule
> Fortunately there is a pretty simple patch to 2.6.2 we can give to
> distribution maintainers who want this to work to keep their system's
> clean. I've included it below.
Hmm, but I can't test for it.
Right now I do
if(cmake >= 2.6.3)
install( to lib/cmake/foo)
install( to lib/foo/cmake)
Which means that if somebody has built KDE with 2.6.3, then he needs 2.6.3 to
build other software using it.
I'm not sure this patch helps a lot.
Or is it time for a 188.8.131.52 ?
More information about the Kde-buildsystem