Alle lunedì 11 maggio 2009, Christophe Giboudeaux ha scritto:
> SVN commit 966746 by cgiboudeaux:
>
> As mentioned by Alex when KDEPIMLIBS_INCLUDE_DIRS was created, installing
> the kdepimlibs CamelCase headers in the same dir as the kdelibs ones is not
> a good idea. (different package -> different dir).
>
> They will now be installed in include/KDEPIMLIBS.

I don't understand the logic behind this move.

Currently, we have the following situation:
- all the .h files from any KDE modules go to $prefix/include
- before this commit, all the CamelCase includes would go $prefix/include/KDE, 
from any KDE module (eg kdelibs, kdepimlibs, kdebase-workspace, kdegames, 
etc)
But now kdepimlibs differs and will install its CamelCase includes in a 
different location. I don't see them conflicting with kdelibs (or other 
modules) ones, so... why?

-- 
Pino Toscano

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem

Reply via email to