[Marble-devel] [Patch] Fix includes so digikam gets compiled if marblewidget is installed

[Jens-Michael Hoffmann]

Hi Torsten,

Am Mittwoch, 16. April 2008 11:17:00 schrieb Torsten Rahn:
> The problem that we are facing right now is the fact that
>
> - Currently we don't intend to guarantee binary compatibility ("BC") until
> KDE 4.2.
>
> - However we are working towards it (by d-pointerifying / pimping various
> classes) already.
>
> - And we encourage "early adopters" like KWorldClock" and "DigiKam" (which
> is meant to be released late this year) to make use of the MarbleWidget
> already. Digikam currently uses Marble 0.5.x as a foundation for their
> integration.
>
> - Marble 0.5.x shipped with lots of headers being installed and some
> distributions actually packaged these separately which has probably led
> several people to the assumption that we would guarantee binary
> compatibility.
>
> - To minimize the harm we currently try to install as few headers as
> possible in Marble-SVN (which will become 0.6 for KDE 4.2) and try to
> d-pointerify those classes affected.
>
> Laurent, Gilles, Jens-Michael: Do you have any suggestion how to handle
> this best?

Well like you said before, we should minimize the include statements in the 
published header(s). d-pointers are certainly the way to go.
Which header files are really needed?

I can prepare a few patches if you like or is someone else working there at 
the moment?

Best regards

Jens-Michael

ps: I've got a small test program which loads tiles from OpenStreetMap :-)