OpenGL support?

Hi,

somehow Marble is broken, always pushing ASSERT messages to the console, so
I'm not able to start digiKam 0.10 anymore. So I started ccmake and disabled
the marble support and also openGL, because my laptop is not working with 3D
acceleration.
Now I noticed that the light table starts 5 times faster (before it took
nearly 5 seconds, now it starts in less than 1 second). I guess this has
nothing to do with marble so the only option left is the openGL support.

Now the actual question :-)
What does the openGL support do in digiKam? Is it for the advanced viewer? And
if so, why is it slowing down light table?

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

another note: digiKam really is fast now, I always was disappointed by the
speed of the 0.10.x series. Maybe a lot users might have the same issue, too.
Shouldn't openGL support be turned off by default?

Andi

On Friday 25 July 2008 18:21:42 Andi Clemens wrote:

> Hi,
>
> somehow Marble is broken, always pushing ASSERT messages to the console, so
> I'm not able to start digiKam 0.10 anymore. So I started ccmake and
> disabled the marble support and also openGL, because my laptop is not
> working with 3D acceleration.
> Now I noticed that the light table starts 5 times faster (before it took
> nearly 5 seconds, now it starts in less than 1 second). I guess this has
> nothing to do with marble so the only option left is the openGL support.
>
> Now the actual question :-)
> What does the openGL support do in digiKam? Is it for the advanced viewer?
> And if so, why is it slowing down light table?
>
> Andi
> _______________________________________________
> 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/7/25 Andi Clemens <[hidden email]>:
>
> another note: digiKam really is fast now, I always was disappointed by the
> speed of the 0.10.x series. Maybe a lot users might have the same issue, too.
> Shouldn't openGL support be turned off by default?

You ave the response. For me OpenGL under Linux is a shame. The
interface to Graphics card is a big puzzle. It will nerver work
properlly like this.

Look like the DirectX interface work better under M$ Os. We need
something like that under Linux.

This is why i never use OpenGL on my computer and i not agree to
implement OpenGL support in digiKAm core. For the moment, it's a waste
of time.

Best

Gilles

>
> Andi
>
> On Friday 25 July 2008 18:21:42 Andi Clemens wrote:
>> Hi,
>>
>> somehow Marble is broken, always pushing ASSERT messages to the console, so
>> I'm not able to start digiKam 0.10 anymore. So I started ccmake and
>> disabled the marble support and also openGL, because my laptop is not
>> working with 3D acceleration.
>> Now I noticed that the light table starts 5 times faster (before it took
>> nearly 5 seconds, now it starts in less than 1 second). I guess this has
>> nothing to do with marble so the only option left is the openGL support.
>>
>> Now the actual question :-)
>> What does the openGL support do in digiKam? Is it for the advanced viewer?
>> And if so, why is it slowing down light table?
>>
>> Andi
>> _______________________________________________
>> 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

But it is turned on / built in at the moment? Or why is it running faster
without openGL here?

Andi

On Friday 25 July 2008 20:37:38 Gilles Caulier wrote:

> 2008/7/25 Andi Clemens <[hidden email]>:
> > another note: digiKam really is fast now, I always was disappointed by
> > the speed of the 0.10.x series. Maybe a lot users might have the same
> > issue, too. Shouldn't openGL support be turned off by default?
>
> You ave the response. For me OpenGL under Linux is a shame. The
> interface to Graphics card is a big puzzle. It will nerver work
> properlly like this.
>
> Look like the DirectX interface work better under M$ Os. We need
> something like that under Linux.
>
> This is why i never use OpenGL on my computer and i not agree to
> implement OpenGL support in digiKAm core. For the moment, it's a waste
> of time.
>
> Best
>
> Gilles
>
> > Andi
> >
> > On Friday 25 July 2008 18:21:42 Andi Clemens wrote:
> >> Hi,
> >>
> >> somehow Marble is broken, always pushing ASSERT messages to the console,
> >> so I'm not able to start digiKam 0.10 anymore. So I started ccmake and
> >> disabled the marble support and also openGL, because my laptop is not
> >> working with 3D acceleration.
> >> Now I noticed that the light table starts 5 times faster (before it took
> >> nearly 5 seconds, now it starts in less than 1 second). I guess this has
> >> nothing to do with marble so the only option left is the openGL support.
> >>
> >> Now the actual question :-)
> >> What does the openGL support do in digiKam? Is it for the advanced
> >> viewer? And if so, why is it slowing down light table?
> >>
> >> Andi
> >> _______________________________________________
> >> 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

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

Dnia Friday 25 of July 2008, Andi Clemens napisał:
> another note: digiKam really is fast now, I always was disappointed by
> the speed of the 0.10.x series. Maybe a lot users might have the same
> issue, too. Shouldn't openGL support be turned off by default?

+1

How you disabled OpenGL stuff?

m.

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

just start ccmake in your build dir and toggle "WITH OPENGL". After that
press "c" and if this succeeded, press "g" to generate the new makefiles.

Maybe it would be better to remove the build dir first, at least for me it
still tried to link against openGL and marble... or at least do a "make
clean" in the digikam/digikam folder.

Andi


On Friday 25 July 2008 21:40:36 Mikolaj Machowski wrote:

> Dnia Friday 25 of July 2008, Andi Clemens napisał:
> > another note: digiKam really is fast now, I always was disappointed by
> > the speed of the 0.10.x series. Maybe a lot users might have the same
> > issue, too. Shouldn't openGL support be turned off by default?
>
> +1
>
> How you disabled OpenGL stuff?
>
> m.
>
> _______________________________________________
> 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]

No idea. the only parts witch use OpenGL are 2 kipi-plugins (slideshow
and imageviewer). But for both opengl is only intialized when plugins
are started.

... or perhaps something happen in Qt core when opengl is used...

Other question is about marble. I don't know if opengl is used here.

Gilles

2008/7/25 Andi Clemens <[hidden email]>:

> But it is turned on / built in at the moment? Or why is it running faster
> without openGL here?
>
> Andi
>
> On Friday 25 July 2008 20:37:38 Gilles Caulier wrote:
>> 2008/7/25 Andi Clemens <[hidden email]>:
>> > another note: digiKam really is fast now, I always was disappointed by
>> > the speed of the 0.10.x series. Maybe a lot users might have the same
>> > issue, too. Shouldn't openGL support be turned off by default?
>>
>> You ave the response. For me OpenGL under Linux is a shame. The
>> interface to Graphics card is a big puzzle. It will nerver work
>> properlly like this.
>>
>> Look like the DirectX interface work better under M$ Os. We need
>> something like that under Linux.
>>
>> This is why i never use OpenGL on my computer and i not agree to
>> implement OpenGL support in digiKAm core. For the moment, it's a waste
>> of time.
>>
>> Best
>>
>> Gilles
>>
>> > Andi
>> >
>> > On Friday 25 July 2008 18:21:42 Andi Clemens wrote:
>> >> Hi,
>> >>
>> >> somehow Marble is broken, always pushing ASSERT messages to the console,
>> >> so I'm not able to start digiKam 0.10 anymore. So I started ccmake and
>> >> disabled the marble support and also openGL, because my laptop is not
>> >> working with 3D acceleration.
>> >> Now I noticed that the light table starts 5 times faster (before it took
>> >> nearly 5 seconds, now it starts in less than 1 second). I guess this has
>> >> nothing to do with marble so the only option left is the openGL support.
>> >>
>> >> Now the actual question :-)
>> >> What does the openGL support do in digiKam? Is it for the advanced
>> >> viewer? And if so, why is it slowing down light table?
>> >>
>> >> Andi
>> >> _______________________________________________
>> >> 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
>
> _______________________________________________
> 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

Dnia Saturday 26 of July 2008, Gilles Caulier napisał:
> No idea. the only parts witch use OpenGL are 2 kipi-plugins (slideshow
> and imageviewer). But for both opengl is only intialized when plugins
> are started.

I think this is just copy'n'paste from global cmake files where OpenGL
is desired for Plasma and KWin. And I admit it has its uses there.

> ... or perhaps something happen in Qt core when opengl is used...
>
> Other question is about marble. I don't know if opengl is used here.
>

Yes. OpenGL is used to accelerate rendering of globe and
transformations.

m.

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

[Gilles Caulier-4]

2008/7/26 Mikolaj Machowski <[hidden email]>:

> Dnia Saturday 26 of July 2008, Gilles Caulier napisał:
>> No idea. the only parts witch use OpenGL are 2 kipi-plugins (slideshow
>> and imageviewer). But for both opengl is only intialized when plugins
>> are started.
>
> I think this is just copy'n'paste from global cmake files where OpenGL
> is desired for Plasma and KWin. And I admit it has its uses there.
>
>> ... or perhaps something happen in Qt core when opengl is used...
>>
>> Other question is about marble. I don't know if opengl is used here.
>>
>
> Yes. OpenGL is used to accelerate rendering of globe and
> transformations.
>

You want mean that OPenGL can be used to accelerate. Here OPenGL is
disable and marble wrok very well...

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

Dnia Saturday 26 of July 2008, Gilles Caulier napisał:

> 2008/7/26 Mikolaj Machowski <[hidden email]>:
> > Dnia Saturday 26 of July 2008, Gilles Caulier napisał:
> >> No idea. the only parts witch use OpenGL are 2 kipi-plugins
> >> (slideshow and imageviewer). But for both opengl is only intialized
> >> when plugins are started.
> >
> > I think this is just copy'n'paste from global cmake files where OpenGL
> > is desired for Plasma and KWin. And I admit it has its uses there.
> >
> >> ... or perhaps something happen in Qt core when opengl is used...
> >>
> >> Other question is about marble. I don't know if opengl is used here.
> >
> > Yes. OpenGL is used to accelerate rendering of globe and
> > transformations.
>
> You want mean that OPenGL can be used to accelerate. Here OPenGL is
> disable and marble wrok very well...

True. On my machine (pretty old, over 6 years now) I didn't spot any
differences in working of Marble widget - the same slowness ;)

Overall with OpenGL disabled (thanks Andi!) I didn't notice major
speed up when digiKam. Maybe little faster. With testing collection
(2000 images grouped in several big folders) 0.10 feels faster than 0.9
but this collection has much smaller database in elements.

m.

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

Well it is faster on my machine but maybe because I disabled marble completely
(I can't compile it since 2 days so I turned the support off). So maybe the
slowness here is no openGL but a marble issue.

Andi

On Saturday 26 July 2008 14:51:54 Mikolaj Machowski wrote:

> Dnia Saturday 26 of July 2008, Gilles Caulier napisał:
> > 2008/7/26 Mikolaj Machowski <[hidden email]>:
> > > Dnia Saturday 26 of July 2008, Gilles Caulier napisał:
> > >> No idea. the only parts witch use OpenGL are 2 kipi-plugins
> > >> (slideshow and imageviewer). But for both opengl is only intialized
> > >> when plugins are started.
> > >
> > > I think this is just copy'n'paste from global cmake files where OpenGL
> > > is desired for Plasma and KWin. And I admit it has its uses there.
> > >
> > >> ... or perhaps something happen in Qt core when opengl is used...
> > >>
> > >> Other question is about marble. I don't know if opengl is used here.
> > >
> > > Yes. OpenGL is used to accelerate rendering of globe and
> > > transformations.
> >
> > You want mean that OPenGL can be used to accelerate. Here OPenGL is
> > disable and marble wrok very well...
>
> True. On my machine (pretty old, over 6 years now) I didn't spot any
> differences in working of Marble widget - the same slowness ;)
>
> Overall with OpenGL disabled (thanks Andi!) I didn't notice major
> speed up when digiKam. Maybe little faster. With testing collection
> (2000 images grouped in several big folders) 0.10 feels faster than 0.9
> but this collection has much smaller database in elements.
>
> m.
>
> _______________________________________________
> 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

[Marcel Wiesweg]

> Hi,
>
> somehow Marble is broken, always pushing ASSERT messages to the console, so
> I'm not able to start digiKam 0.10 anymore. So I started ccmake and
> disabled the marble support and also openGL, because my laptop is not
> working with 3D acceleration.
> Now I noticed that the light table starts 5 times faster (before it took
> nearly 5 seconds, now it starts in less than 1 second). I guess this has
> nothing to do with marble so the only option left is the openGL support.

I think at the bottom of the thread there is a conclusion that Marble is the
culprit here. The lighttable has two sidebars, and each sidebar hosts a
Marble widget. You cannot test, but when I start digikam (currently with an
old version of Marble) I can see by debug statements that initializing Marble
takes considerable time (a few secs). I expect initialization time for
Marble, that's ok. There are two fields how we / the Marble team can work on
this:
- Find out if we can delay the initialization of Marble until the relevant
sidebar is opened by the user. This can depend on Marble moving
initialization tasks to a thread
- Find out if Marble is optimized for using more than one widget instance in
an application (we easily use several), or if perhaps more data sharing is
possible

Of course, all this is work secondary to having a stable and maintained
Marble.

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

The question is do we really need those side bars in the lighttable? If I open
both of them, I can't even see my images with a 1024x768 resolution anymore.
The sidebars are wasting too much space.
Second question: If the sidebars are really necessary, can't we use the marble
widgets from the main window somehow?
They should already be initialized. So when switching windows (main window,
light table) the instances of the marble widgets are refreshed by the current
view and current selected image.
Or wouldn't it be even possible to initialize the light table on startup (and
the two other marble widgets), so that using it for the first time will start
it faster?
The light table window is kept when used once, so we could also initialize it
anyway when digiKam is starting up?

Andi

On Saturday 26 July 2008 16:43:51 Marcel Wiesweg wrote:

> > Hi,
> >
> > somehow Marble is broken, always pushing ASSERT messages to the console,
> > so I'm not able to start digiKam 0.10 anymore. So I started ccmake and
> > disabled the marble support and also openGL, because my laptop is not
> > working with 3D acceleration.
> > Now I noticed that the light table starts 5 times faster (before it took
> > nearly 5 seconds, now it starts in less than 1 second). I guess this has
> > nothing to do with marble so the only option left is the openGL support.
>
> I think at the bottom of the thread there is a conclusion that Marble is
> the culprit here. The lighttable has two sidebars, and each sidebar hosts a
> Marble widget. You cannot test, but when I start digikam (currently with an
> old version of Marble) I can see by debug statements that initializing
> Marble takes considerable time (a few secs). I expect initialization time
> for Marble, that's ok. There are two fields how we / the Marble team can
> work on this:
> - Find out if we can delay the initialization of Marble until the relevant
> sidebar is opened by the user. This can depend on Marble moving
> initialization tasks to a thread
> - Find out if Marble is optimized for using more than one widget instance
> in an application (we easily use several), or if perhaps more data sharing
> is possible
>
> Of course, all this is work secondary to having a stable and maintained
> Marble.
>
> Marcel
> _______________________________________________
> 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

Dnia Saturday 26 of July 2008, Andi Clemens napisał:
> The question is do we really need those side bars in the lighttable? If
> I open both of them, I can't even see my images with a 1024x768
> resolution anymore. The sidebars are wasting too much space.

Sidebars are necessary due to insufficient image information in
thumbbar.

> Second question: If the sidebars are really necessary, can't we use the
> marble widgets from the main window somehow?

Not all info is needed in Light Table. For example Tag Filters panel is
already filtered out ;)

m.

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

[Marcel Wiesweg]

> The question is do we really need those side bars in the lighttable? If I
> open both of them, I can't even see my images with a 1024x768 resolution
> anymore. The sidebars are wasting too much space.

You can hide the sidebars - I would assume they are hidden by default (?).
That the minimum size of the sidebars is currently so large is a problem. I
have not yet tested out which widget is the limiting factor.

> Second question: If the sidebars are really necessary, can't we use the
> marble widgets from the main window somehow?
> They should already be initialized. So when switching windows (main window,
> light table) the instances of the marble widgets are refreshed by the
> current view and current selected image.

I suspect that from within Marble there is a good potential to optimize for
applications with more than one instance of the widget. Judging from the
debug messages, loading plugins, cache files and parsing data files is done
each time again.

> Or wouldn't it be even possible to initialize the light table on startup
> (and the two other marble widgets), so that using it for the first time
> will start it faster?
> The light table window is kept when used once, so we could also initialize
> it anyway when digiKam is starting up?

Users who never use the lighttable will endure a longer startup time and more
memory footprint then.

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

[Gerhard Kulzer-3]

I compiled marble from svn today, then digikam: It really loads several times faster.

Gerhard

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

Are you really able to link digiKam against marble?
Since a few days I can't do this anymore. I removed my build dir, checkout
everything new, recompiled marble, but somehow I always get this message:

===================================================
In file included
from /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/digikam_bin_automoc.cpp:3:
/home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:
In member function ‘virtual void* Digikam::GPSSearchWidget::qt_metacast(const
char*)’:
/home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:56:
error: cannot call member function ‘virtual void* QLabel::qt_metacast(const
char*)’ without object
/home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:
In member function ‘virtual int
Digikam::GPSSearchWidget::qt_metacall(QMetaObject::Call, int, void**)’:
/home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:61:
error: cannot call member function ‘virtual int
QLabel::qt_metacall(QMetaObject::Call, int, void**)’ without object
make[2]: ***
[digikam/digikam/CMakeFiles/digikam_bin.dir/digikam_bin_automoc.o] Error 1
make[2]: Leaving directory `/home/andi/Programmieren/workspace/digikam_KDE4'
make[1]: *** [digikam/digikam/CMakeFiles/digikam_bin.dir/all] Error 2
make[1]: Leaving directory `/home/andi/Programmieren/workspace/digikam_KDE4'
make: *** [all] Error 2
===================================================


If I disable marble widget in digiKam cmake config, it is working.

Andi


On Wednesday 30 July 2008 07:07:40 Gerhard Kulzer wrote:
> I compiled marble from svn today, then digikam: It really loads several
> times faster.
>
> Gerhard

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

[Gilles Caulier-4]

Andi,

I have no problem here. I update marble every day and install it as
well in my system.

Gilles

2008/7/30 Andi Clemens <[hidden email]>:

> Are you really able to link digiKam against marble?
> Since a few days I can't do this anymore. I removed my build dir, checkout
> everything new, recompiled marble, but somehow I always get this message:
>
> ===================================================
> In file included
> from /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/digikam_bin_automoc.cpp:3:
> /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:
> In member function 'virtual void* Digikam::GPSSearchWidget::qt_metacast(const
> char*)':
> /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:56:
> error: cannot call member function 'virtual void* QLabel::qt_metacast(const
> char*)' without object
> /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:
> In member function 'virtual int
> Digikam::GPSSearchWidget::qt_metacall(QMetaObject::Call, int, void**)':
> /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpssearchwidget.cpp:61:
> error: cannot call member function 'virtual int
> QLabel::qt_metacall(QMetaObject::Call, int, void**)' without object
> make[2]: ***
> [digikam/digikam/CMakeFiles/digikam_bin.dir/digikam_bin_automoc.o] Error 1
> make[2]: Leaving directory `/home/andi/Programmieren/workspace/digikam_KDE4'
> make[1]: *** [digikam/digikam/CMakeFiles/digikam_bin.dir/all] Error 2
> make[1]: Leaving directory `/home/andi/Programmieren/workspace/digikam_KDE4'
> make: *** [all] Error 2
> ===================================================
>
>
> If I disable marble widget in digiKam cmake config, it is working.
>
> Andi
>
>
> On Wednesday 30 July 2008 07:07:40 Gerhard Kulzer wrote:
>> I compiled marble from svn today, then digikam: It really loads several
>> times faster.
>>
>> Gerhard
>
> _______________________________________________
> 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

Me too... normally all is fine... maybe a kde4libs problem? This is the only
thing I updated recently.

Andi

On Wednesday 30 July 2008 10:44:39 Gilles Caulier wrote:

> Andi,
>
> I have no problem here. I update marble every day and install it as
> well in my system.
>
> Gilles
>
> 2008/7/30 Andi Clemens <[hidden email]>:
> > Are you really able to link digiKam against marble?
> > Since a few days I can't do this anymore. I removed my build dir,
> > checkout everything new, recompiled marble, but somehow I always get this
> > message:
> >
> > ===================================================
> > In file included
> > from
> > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/digikam_b
> >in_automoc.cpp:3:
> > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpsse
> >archwidget.cpp: In member function 'virtual void*
> > Digikam::GPSSearchWidget::qt_metacast(const char*)':
> > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpsse
> >archwidget.cpp:56: error: cannot call member function 'virtual void*
> > QLabel::qt_metacast(const char*)' without object
> > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpsse
> >archwidget.cpp: In member function 'virtual int
> > Digikam::GPSSearchWidget::qt_metacall(QMetaObject::Call, int, void**)':
> > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gpsse
> >archwidget.cpp:61: error: cannot call member function 'virtual int
> > QLabel::qt_metacall(QMetaObject::Call, int, void**)' without object
> > make[2]: ***
> > [digikam/digikam/CMakeFiles/digikam_bin.dir/digikam_bin_automoc.o] Error
> > 1 make[2]: Leaving directory
> > `/home/andi/Programmieren/workspace/digikam_KDE4' make[1]: ***
> > [digikam/digikam/CMakeFiles/digikam_bin.dir/all] Error 2 make[1]: Leaving
> > directory `/home/andi/Programmieren/workspace/digikam_KDE4' make: ***
> > [all] Error 2
> > ===================================================
> >
> >
> > If I disable marble widget in digiKam cmake config, it is working.
> >
> > Andi
> >
> > On Wednesday 30 July 2008 07:07:40 Gerhard Kulzer wrote:
> >> I compiled marble from svn today, then digikam: It really loads several
> >> times faster.
> >>
> >> Gerhard
> >
> > _______________________________________________
> > 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

It seems to work now... I disabled marble again, compiled, enabled it again,
compiled and now it works. CMakeCache broken? Anyway it is working now.

Andi

On Wednesday 30 July 2008 10:46:17 Andi Clemens wrote:

> Me too... normally all is fine... maybe a kde4libs problem? This is the
> only thing I updated recently.
>
> Andi
>
> On Wednesday 30 July 2008 10:44:39 Gilles Caulier wrote:
> > Andi,
> >
> > I have no problem here. I update marble every day and install it as
> > well in my system.
> >
> > Gilles
> >
> > 2008/7/30 Andi Clemens <[hidden email]>:
> > > Are you really able to link digiKam against marble?
> > > Since a few days I can't do this anymore. I removed my build dir,
> > > checkout everything new, recompiled marble, but somehow I always get
> > > this message:
> > >
> > > ===================================================
> > > In file included
> > > from
> > > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/digikam
> > >_b in_automoc.cpp:3:
> > > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gps
> > >se archwidget.cpp: In member function 'virtual void*
> > > Digikam::GPSSearchWidget::qt_metacast(const char*)':
> > > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gps
> > >se archwidget.cpp:56: error: cannot call member function 'virtual void*
> > > QLabel::qt_metacast(const char*)' without object
> > > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gps
> > >se archwidget.cpp: In member function 'virtual int
> > > Digikam::GPSSearchWidget::qt_metacall(QMetaObject::Call, int, void**)':
> > > /home/andi/Programmieren/workspace/digikam_KDE4/digikam/digikam/moc_gps
> > >se archwidget.cpp:61: error: cannot call member function 'virtual int
> > > QLabel::qt_metacall(QMetaObject::Call, int, void**)' without object
> > > make[2]: ***
> > > [digikam/digikam/CMakeFiles/digikam_bin.dir/digikam_bin_automoc.o]
> > > Error 1 make[2]: Leaving directory
> > > `/home/andi/Programmieren/workspace/digikam_KDE4' make[1]: ***
> > > [digikam/digikam/CMakeFiles/digikam_bin.dir/all] Error 2 make[1]:
> > > Leaving directory `/home/andi/Programmieren/workspace/digikam_KDE4'
> > > make: *** [all] Error 2
> > > ===================================================
> > >
> > >
> > > If I disable marble widget in digiKam cmake config, it is working.
> > >
> > > Andi
> > >
> > > On Wednesday 30 July 2008 07:07:40 Gerhard Kulzer wrote:
> > >> I compiled marble from svn today, then digikam: It really loads
> > >> several times faster.
> > >>
> > >> Gerhard
> > >
> > > _______________________________________________
> > > 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

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