[Kde-pim] Building Akonadi resources outside kdepim-runtime no longer works

[David Jarvie]

Before kdepim and kdepim-runtime were split into separate git modules, it was possible to build KAlarm with its own Akonadi resource, whose code is in the kalarm directory. This no longer works, since there is no fixed path relationship between the kdepim and kdepim-runtime source directories.

I'd prefer to keep the code in kdepim/kalarm at least until it is all tested much better, but kdepim-runtime doesn't install headers, so it isn't obviously feasible. Is there any way to allow KAlarm resources to be built other than to move the code into kdepim-runtime? If this IS necessary, how can code be moved between the two git modules?

Is there a long term aim to allow custom resources to be developed outside kdepim-runtime? The same problem as described above could easily arise for other applications in the future which are not part of kdepim, but which need their own resource types, possibly modifications of the existing kdepim-runtime resources.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20101228/7cee59c6/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/