KDE/kdepimlibs
Pino Toscano
toscano.pino at tiscali.it
Tue May 12 18:20:53 CEST 2009
Alle martedì 12 maggio 2009, Andreas Pakulat ha scritto:
> > to $prefix/include/KDEPimLibs.
> > Isn't $prefix/include/KDE "namespaced" already?
>
> Yes, across all of KDE main modules, which might or might not be enough. If
> KDevPlatform would install camelcase versions of its public API into
> prefix/include/KDE we'd most probably have naming clashes rather sooner
> than later because of:
>
> IPlugin
> ICore
> IAssistant
> ISession
> ProjectModel
>
> and possibly more. And namespacing those files with KDev_ would obviously
> defeat the purpose of the camelcase includes.
And in such case, you would do like it has been done so far: grouping by
namespace:
- $prefix/include/KDE/Plasma/Dialog for namespace Plasma { class Dialog; }
- $prefix/include/KDE/KCal/Alarm for namespace KCal { class Calendar; }
- $prefix/include/KDE/DOM for KHTML's DOM classes in namespace DOM
that, in your case, would be
- $prefix/include/KDE/KDevelop/IAssistan for namespace KDevelop { class
IAssistant }
Don't see anything bad in doing that. Especially in case of kdepimlibs, whose
classes are already grouped in such way (see
kdepimlibs/includes/CMakeLists.txt), so you would not see
$prefix/include/KDE/Calendar.
--
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20090512/42d47f8c/attachment.sig
More information about the Kde-buildsystem
mailing list