On Monday 08 July 2013, Alexander Neundorf wrote:
> On Friday 05 July 2013, Alex Merry wrote:
> > On 04/07/13 22:44, David Faure wrote:
> > > diff --git a/src/plasmapkg/CMakeLists.txt
> > > b/src/plasmapkg/CMakeLists.txt index d2f2427..919dd64 100644
> > > --- a/src/plasmapkg/CMakeLists.txt
> > > +++ b/src/plasmapkg/CMakeLists.txt
> > > @@ -5,7 +5,7 @@ add_executable(plasmapkg
> > >
> > > plasmapkg.cpp
> > >
> > > )
> > >
> > > -target_link_libraries(plasmapkg kdeqt5staging plasma)
> > > +target_link_libraries(plasmapkg kdeqt5staging plasma kde4support)
> > >
> > > message("INSTALL_TARGETS_DEFAULT_ARGS
> > > ${INSTALL_TARGETS_DEFAULT_ARGS}")
> > >
> > > ... gives the error ....
> > >
> > > ld: cannot find -lkde4support
> >
> > So... most of the FooConfig.cmake files appear to call out to an
> > equivalent FooTarget.cmake file, which in turn loads something like
> > FooTarget-debug.cmake, which appears to set target properties telling
> > cmake where to find the libraries in question.
> >
> > kde4supportConfig.cmake does not do this. In fact, it even has an
> > include line for a targets file commented out.
> >
> > I guess this could be the reason?
>
> Yes.
> I'll have a look tomorrow how to do it properly, whether fix
> kde4supportConfig.cmake or whether to put the kde4support target into
> KDELibs4Config.cmake, depending on the dependencies.
kde4support still links e.g. against kdeui and kio.
So I think I'll make it part of KDELibs4 for now.
So no
find_package(KDE4Support)
for now,
but find_package(KDELibs4)
and after that you'll be able to use the "kde4support" imported target
directly or somne LIBRARY variable.
Alex
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
