Digikam git build without marble issue

Gilles Caulier caulier.gilles at gmail.com
Tue Dec 12 05:28:27 GMT 2023


Hi,

This must be fixed in git/master with last commit.

There is a new cmake option 'ENABLE_GEOLOCATION", ON by default

Best

Gilles Caulier

Le lun. 11 déc. 2023 à 22:34, <leoutation at gmx.fr> a écrit :
>
> On 12/11/23 21:38, Maik Qualmann wrote:
> > That's interesting that you have it with Linux, we have this bug report for
> > Windows:
> >
> > https://bugs.kde.org/show_bug.cgi?id=477853
>
> I can't reproduce this issue on Linux with about 20.000 images
> Digikam starts normally, not slowly but i have to say it starts
> directly, without any scan/cleaning albums/db. If i would enable 'scan
> for new items at startup', it should be very very slow.
> Its seems db maintenance is slow.  May be because it's first time i use
> Digikam Qt6 with this db?
> I have to test more
> >
> > All users report that the Windows version compiled with Qt5 is running
> > normally again. However, we are creating the Windows version with the
> > Microsoft compiler for the first time.
> >
> > I can't reproduce it myself, what type of database are you using?
>
> I use Mariadb external server. I checked it with Mariadb tool
> 'mariadb-check', there is no problem
>
> >
> > Maik
> >
> > Am Montag, 11. Dezember 2023, 21:22:09 CET schrieb leoutation at gmx.fr:
> >> On 12/11/23 20:28, Maik Qualmann wrote:
> >>> Yes, digiKam from git/master currently compiles with Qt6. Gilles is
> >>> currently porting back to Qt5 support. You have to wait...
> >>>
> >>> Maik
> >>
> >> I already built today digikam with Qt6 and KF6 (thanks to 'kde-unstable'
> >> Arch Linux repo packager https://archlinux.org/packages/?repo=KDE-Unstable)
> >> It works but it seems maintenance, database cleaning, scan new items,
> >> etc, take more time than with Qt5 version. I have to test more...
> >>
> >>> Am Montag, 11. Dezember 2023, 19:56:16 CET schrieb leoutation at gmx.fr:
> >>>> On 12/11/23 18:45, Maik Qualmann wrote:
> >>>>> No, that's not a mistake, we are in the process of integrating Marble
> >>>>> into
> >>>>> digiKam. Since the Marble team did not respond to requests for porting
> >>>>> to
> >>>>> Qt6, Gilles did the porting. This means we can also offer Marble with
> >>>>> Qt6, otherwise we would lose the geolocation function. We are currently
> >>>>> working on making it work again under Qt5. It is a reduced marble
> >>>>> library
> >>>>> that is tailored to the needs of digiKam. And before the bug report
> >>>>> comes, we might also integrate an OFF switch.
> >>>>>
> >>>>> Maik
> >>>>
> >>>> Thanks for these explanations
> >>>>
> >>>> /home/fre/ARCH-AUR/digikam-git-light/src/digikam/core/utilities/geolocati
> >>>> on/ marble/GeoGraphicsScene.cpp:232:52: error: ‘T& QMultiHash<K,
> >>>> V>::operator[](const Key&) [with Key =
> >>>> Marble::TileId; T = QHash<const Marble::GeoDataFeature*,
> >>>> Marble::GeoGraphicsItem*>]’ is private within this context
> >>>>
> >>>>      232 |         auto & tileList = d->m_tiledItems[*tileIter];
> >>>>
> >>>>          |                                                    ^
> >>>>
> >>>> In file included from /usr/include/qt/QtCore/QHash:1,
> >>>>
> >>>>                     from
> >>>>
> >>>> /home/fre/ARCH-AUR/digikam-git-light/src/digikam/core/utilities/geolocati
> >>>> on/ marble/geodata/data/GeoDataLatLonAltBox.h:18, from
> >>>> /home/fre/ARCH-AUR/digikam-git-light/src/digikam/core/utilities/geolocati
> >>>> on/ marble/GeoGraphicsScene.cpp:9: /usr/include/qt/QtCore/qhash.h:1117:8:
> >>>> note: declared private here 1117 |     T &operator[](const Key &key);
> >>>>
> >>>>          |        ^~~~~~~~
> >>>>
> >>>> /home/fre/ARCH-AUR/digikam-git-light/src/digikam/core/utilities/geolocati
> >>>> on/ marble/GeoGraphicsScene.cpp: In member function ‘void
> >>>> Marble::GeoGraphicsScene::addItem(Marble::GeoGraphicsItem*)’:
> >>>> /home/fre/ARCH-AUR/digikam-git-light/src/digikam/core/utilities/geolocati
> >>>> on/ marble/GeoGraphicsScene.cpp:269:42: error: ‘T& QMultiHash<K,
> >>>> V>::operator[](const Key&) [with Key =
> >>>> Marble::TileId; T = QHash<const Marble::GeoDataFeature*,
> >>>> Marble::GeoGraphicsItem*>]’ is private within this context
> >>>>
> >>>>      269 |     auto & tileList = d->m_tiledItems[key];
> >>>>
> >>>>          |                                          ^
> >>>>
> >>>> /usr/include/qt/QtCore/qhash.h:1117:8: note: declared private here
> >>>>
> >>>>     1117 |     T &operator[](const Key &key);
> >>>>
> >>>>          |        ^~~~~~~~
> >>>>
> >>>> make[2]: ***
> >>>> [core/utilities/geolocation/marble/CMakeFiles/core_marble_obj.dir/build.m
> >>>> ake>>
> >>>> :9150:
> >>>> core/utilities/geolocation/marble/CMakeFiles/core_marble_obj.dir/GeoGraph
> >>>> ic
> >>>> sScene.cpp.o] Error 1
> >>>>
> >>>>> Am Montag, 11. Dezember 2023, 17:50:58 CET schrieb leoutation at gmx.fr:
> >>>>>> Hi
> >>>>>> Usually,  I successfully build Digikam git without marble because it's
> >>>>>> optional.
> >>>>>> I see now Digikam build process strangely finds libmarble on my system
> >>>>>> but i don't have any 'marble' package/library installed on my system
> >>>>>>
> >>>>>>      libmarble found.......................... YES (optional)
> >>>>>>
> >>>>>> I think it's a bug
> >>>>>> conditions: Arch system QT5 KF5
> >>>>>>
> >>>>>> --
> >>>>>> Maderios
> >>>>
> >>>> --
> >>>> Maderios
> >>
> >> --
> >> Maderios
> >
> >
> >
> >
>
> --
> Maderios
>


More information about the Digikam-users mailing list