Reducing excess linkage - cmake 2.6 IMPORTED targets and LINK_INTERFACE_LIBRARIES for kdelibs
Dirk Mueller
mueller at kde.org
Tue May 6 22:41:29 CEST 2008
On Monday 28 April 2008, Alexander Neundorf wrote:
> -cmake 2.6.0 is not released yet and we are already at alpha1 stage of KDE
> 4.1 -the patches kind-of break source compatibility
not really.. apps that break due to that are invalid anyway. for every 3rd
party module which we depend on and that switches away from libtool we run
into the same issue (e.g. libvorbis just recently pops up my mind). And then
again, binary compatibiliy is what counts - not source compatibility. and
binary compatibility is not broken, as long as the app links all that it
needs directly by itself.
> , stuff which links with
> KDE 4.0.x may not link anymore once this patch is applied
thats the reason why the patch should be applied to be able to optionally use
this feature as soon as possible, so that those who care (I count debian and
opensuse packagers here) can iron out all the quirks and fix all the failing
packages before users stumble over it. I could add it to the dashboard so
that we can see the failures right away.
> Depending on how we deal with the compatibility problem, I'd like to do
> this once trunk is open for KDE 4.2 and require cmake 2.6.x by then, so
> *every* developer will notice when something breaks. Then we'll also have
> time to make sure at least the sources in KDE svn build properly.
Thats one solution - another solution is to make it optinally available now,
so that distributions can fix the migration path, and make it a requirement
with KDE 4.2 (or maybe even 4.1).
Greetings,
Dirk
More information about the Kde-buildsystem
mailing list