Patch for marble compile error

Hi,

Marble moved from global namespace to the marble namespace. I couldn't build
it with a new kdeedu so I had a look why it didn't build and it was quite easy
to fix. The patch is in the attachment. If you have questions, please CC to me,
because I'm not subscribed to the list, but I guess it's not necessary.

Best Regards,
Mathias Kraus

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Andi, patch is fine... but,

...alternative way and certainly more simple to use is just to put :

using namespace Marble;

...just on the top of source files, like this it will compile again
with old version of Marble.

Gilles



2008/8/17 Mathias Kraus <[hidden email]>:

> Hi,
>
> Marble moved from global namespace to the marble namespace. I couldn't build
> it with a new kdeedu so I had a look why it didn't build and it was quite easy
> to fix. The patch is in the attachment. If you have questions, please CC to me,
> because I'm not subscribed to the list, but I guess it's not necessary.
>
> Best Regards,
> Mathias Kraus
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

It wasn't me... :-)

Andi

On Monday 18 August 2008 06:22:08 Gilles Caulier wrote:

> Andi, patch is fine... but,
>
> ...alternative way and certainly more simple to use is just to put :
>
> using namespace Marble;
>
> ...just on the top of source files, like this it will compile again
> with old version of Marble.
>
> Gilles
>
> 2008/8/17 Mathias Kraus <[hidden email]>:
> > Hi,
> >
> > Marble moved from global namespace to the marble namespace. I couldn't
> > build it with a new kdeedu so I had a look why it didn't build and it was
> > quite easy to fix. The patch is in the attachment. If you have questions,
> > please CC to me, because I'm not subscribed to the list, but I guess it's
> > not necessary.
> >
> > Best Regards,
> > Mathias Kraus
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2008/8/18 Andi Clemens <[hidden email]>:
> It wasn't me... :-)

yes, yes (:=))) but it's just informative. If you want to patch trunk,
let's go. I still busy with Raw Import tool into KDE3 branch

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

A ok, those reply on mailing list looked so "personal"... :-)

Andi


On Monday 18 August 2008 09:35:11 Gilles Caulier wrote:

> 2008/8/18 Andi Clemens <[hidden email]>:
> > It wasn't me... :-)
>
> yes, yes (:=))) but it's just informative. If you want to patch trunk,
> let's go. I still busy with Raw Import tool into KDE3 branch
>
> Gilles
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel