[digiKam-users] Is this the correct appimage?

[Gilles Caulier]

Hi all,

After one night of compilation, the Linux AppImage 32 bits for 6.1.0
pre-release is now online...

https://files.kde.org/digikam/

This take age, because QtWebkit 5.212 is not optimized to compile and link
on 32 bits platform. I restarted the compilation 3 times due to a linker
memory overflow. Each QtWebkit take 2 hours to be completed, and of course
the error come at 100%. This is the Murphy law...

I currently start to investigate to the alternative QtWebEngine to replace
QtWebkit definitively...

Gilles Caulier

Le mer. 20 mars 2019 à 18:55, <digikam at 911networks.com> a écrit :

> Hi Gilles,
>
> Yes, it's working, albeit a little bit slower and no unresolved
> symbols during the start up.
>
> Kernel: 4.19.28-1-MANJARO x86_64 bits: 64
> Desktop: Xfce 4.13.2git-UNKNOWN Distro: Manjaro Linux
>
> Merci
>
> Syv
>
>
> On Wed, 20 Mar 2019 16:50:59 +0100
> Gilles Caulier <caulier.gilles at gmail.com> wrote:
>
> > Hi all,
> >
> > The AppImage 6.1.0 pre-release is back. Only for 64 bits for the
> > moment...
> >
> > https://files.kde.org/digikam/
> >
> > 32 bits is compiling. It take more than 6 hours to be completed.
> >
> > After 3 weeks of intensive tests, i completed these updates :
> >
> > - Qt 5.9.7 => Qt 5.11.3 (I tried last Qt 5.12.2, but it more
> > complex than expected. So i delay this task for later...)
> > - QtWebkit 5.9.1 => 5.212 : this one is used to show geolocation
> > view with GoogleMap. I tried to migrate to QWebEngine, but the
> > puzzle is just enormous. So i delayed with 5.12.2 migration stage.
> > - openssl : last stable version is used and Qt is hard linked with
> > it. So typically the SSL connection with webservices must be fixed
> > now.
> > - ffmpeg 3.3.3 => 3.3.9. I delay later to migrate to 4.1.x, has it's
> > introduce more complex dependencies to solve.
> > - OpenCV 3.4.5 is now compiled with the most small fingerprint to
> > prevent unexpected crash in Face Management. I disabled all
> > optimizations (CUDA, OpenCL, OpenMP, etc...), and only compiled
> > only the sub components required by digiKam to prevent
> > side-effects. This library is really a monster with plenty of
> > options usable at configuration time.
> >
> > I hope that all unresolved symbols at start up will be fixed now.
> > If not, let's me here.
> >
> > Best
> >
> > Gilles Caulier
> >
> >
> >
> >
> >
> >
> > Le lun. 18 mars 2019 à 04:55, Gilles Caulier
> > <caulier.gilles at gmail.com> a écrit :
> >
> > > Current appimage 6.1.0 is broken. do not use it...
> > >
> > > Gilles Caulier
> > >
> > > Le lun. 18 mars 2019 à 01:30, <digikam at 911networks.com> a écrit :
> > >
> > >> The digikam-6.1.0-git-20190317T144548-x86-64.appimage
> > >>
> > >> File information
> > >>
> > >>     Filename: digikam-6.1.0-git-20190317T144548-x86-64.appimage
> > >>     Path: /digikam/digikam-6.1.0-git-20190317T144548-x86-64.appimage
> > >>     Size: 78M (81788928 bytes)
> > >>     Last modified: Sun, 17 Mar 2019 13:51:33 GMT (Unix time:
> > >> 1552830693)
> > >>
> > >>
> > >> It's only 78Mb. It was always in 400Mb range
> > >>
> > >> https://i.imgur.com/gmmIBJE.png
> > >>
> > >> --
> > >> sknahT
> > >>
> > >> vyS
> > >>
> > >
>
>
> --
> sknahT
>
> vyS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190321/93a7df26/attachment.html>