From kde-buildsystem Thu May 14 06:24:11 2009 From: Andreas Pakulat Date: Thu, 14 May 2009 06:24:11 +0000 To: kde-buildsystem Subject: Re: KDE/kdepimlibs Message-Id: <20090514062411.GA22425 () trinity ! apaku ! dnsalias ! org> X-MARC-Message: https://marc.info/?l=kde-buildsystem&m=124228228611548 On 13.05.09 18:37:53, Alexander Neundorf wrote: > On Tuesday 12 May 2009, Pino Toscano wrote: > > Alle marted́ 12 maggio 2009, Christophe Giboudeaux ha scritto: > > > 5/ Considering 1,2 and 3, I still didn't read any valid reason for using > > > the same prefix as kdelibs, kdebase, kdegames etc... and add more files > > > inside /KDE. > > > > Coherency with other modules? > > - all of KDE installs lowercase includes in $prefix/include, CamelCase ones > > in $prefix/include/KDE > > Question here is, what is KDE. > Must any package which links against kdecore install its headers into > include/KDE/ ? > I would see include/KDE/ actually more as the include directory for the > kdelibs module. Why is it include/KDE then? Thats confusing, because the name right now suggests that its the camel-case-header directory for all of KDE. And having include/KDE with for example kdebase libs and koffice libs is even more confusing if kdepimlibs does it all different. > That's also what find_package(KDE4) does, it doesn't find everything > on the system which is KDE-related, it finds only kdelibs. Agree. > I think I agree with Christophe that installing kdepimlibs into its own subdir > would be a good thing. I do understand your point, but IMHO having now one or two modules in include/ but other modules (not only kdelibs, but also kdebase libs) in include/KDE just adds confusion. We should just put this down as todo for KDE5 to use include/ for _all_ modules including kdelibs and leave what we have now so its at least consistent - even though not perfect. > ... > > So, are there other serious reasons, other than that kdepimlibs "looks > > special(?)" wrt the rest of KDE? > > It's how "the rest of KDE" is defined. As I said above, I think it makes sense > to see include/KDE/ as the include dir for the core of KDE, which is kdelibs. I don't, for me include/KDE naturally translates to any core module of KDE (i.e. anything in trunk/KDE). Only include/KDELibs would translate to kdelibs to me. Andreas -- Are you ever going to do the dishes? Or will you change your major to biology? _______________________________________________ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem