[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #51 from [email protected] ---
Git commit adb7178aa0ec3e02ecbf76bb5c29b4544a94a5f8 by Gilles Caulier.
Committed on 10/03/2022 at 07:18.
Pushed by cgilles into branch 'qt5-maintenance'.

As with AppImage, build libaom as static under Windows to link with libavif.
Add 2 new scripts to install/update one dependency in MXE, as with AppImage

M  +20   -27   project/bundles/3rdparty/ext_libavif/CMakeLists.txt
A  +77   -0project/bundles/mxe/tools/installextralibsdep.sh
A  +82   -0project/bundles/mxe/tools/installmxedeps.sh

https://invent.kde.org/graphics/digikam/commit/adb7178aa0ec3e02ecbf76bb5c29b4544a94a5f8

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

[email protected] changed:

   What|Removed |Added

   Version Fixed In||7.7.0
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #50 from [email protected] ---
Git commit fc125e54fa9a67bfb271b0bd5a4a1d4e8bde2d03 by Gilles Caulier.
Committed on 10/03/2022 at 04:52.
Pushed by cgilles into branch 'qt5-maintenance'.

Same type-mime problem than AVIF for JPX, depending of Qt version
Related: bug 436533

M  +4-1core/libs/database/item/scanner/itemscanner_photo.cpp
M  +2-1core/libs/threadimageio/thumb/thumbnailcreator_engine.cpp

https://invent.kde.org/graphics/digikam/commit/fc125e54fa9a67bfb271b0bd5a4a1d4e8bde2d03

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #49 from [email protected] ---
AVIF testfiles:
https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #48 from Maik Qualmann  ---
OK, interesting. I searched the web for more AVIF samples. Images that can be
displayed are actually recognized as AVIF by QImageReader::imageFormat.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #47 from Maik Qualmann  ---
QByteArray QImageReader::imageFormat(const QString &fileName)

This function should return an empty string if the format is unknown (PCX for
me). An empty string is probably not an empty QByteArray. Therefore, the
fallback to the QFileInfo suffix probably does not work.

With the test for the extension in advance, it now works. 

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #46 from Maik Qualmann  ---
Git commit 8c54803387e7af323a9e293359076ba3610c6702 by Maik Qualmann.
Committed on 09/03/2022 at 21:04.
Pushed by mqualmann into branch 'master'.

fix AVIF detection for the database

M  +7-0core/libs/database/item/scanner/itemscanner_photo.cpp

https://invent.kde.org/graphics/digikam/commit/8c54803387e7af323a9e293359076ba3610c6702

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #45 from Maik Qualmann  ---
Hi Gilles,

For me it is recognized as a "PCX" image. Recognition is done with
QImageReader::imageFormat(). So the image format is still unknown in Qt.


https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/database/item/scanner/itemscanner_photo.cpp#L119

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #44 from [email protected] ---
Maik,

For AVIF, the registered image format in database is an empty string.

In fact this is a generic problem. If type mime is empty from QFileInfo, we
must do something at least, not to store an empty string.

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #43 from [email protected] ---
Oh, elementary Mr Watson (:-))

Digikam::ThumbnailCreator::createThumbnail: Trying to get thumbnail from
"/home/gilles/Images/4324477432.avif" ( "" )

The type mime returned from QFileInfo is empty... Too bad...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #42 from [email protected] ---
And now AVIF support on AppImage. Thumbnail work now... 

https://i.imgur.com/JV3Dmoz.png

But the mime-type "AVIF" is not shown as thumb overlay...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #41 from [email protected] ---
Git commit 45fa6f27a17d762489821605fd8c47cf3f056a47 by Gilles Caulier.
Committed on 09/03/2022 at 14:03.
Pushed by cgilles into branch 'qt5-maintenance'.

Try to fix AVIF thumbnail extraction.
I suspect QFileInfo type-mime return video not image

M  +6-1core/libs/threadimageio/thumb/thumbnailcreator_engine.cpp

https://invent.kde.org/graphics/digikam/commit/45fa6f27a17d762489821605fd8c47cf3f056a47

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #40 from [email protected] ---
Git commit c4a373ecc34b5d0511b7f583e43da44115fb2849 by Gilles Caulier.
Committed on 09/03/2022 at 13:46.
Pushed by cgilles into branch 'qt5-maintenance'.

AVIF: preload library from the AppImage bundle.

M  +3-0project/bundles/appimage/data/AppRun

https://invent.kde.org/graphics/digikam/commit/c4a373ecc34b5d0511b7f583e43da44115fb2849

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #39 from [email protected] ---
Git commit 1a34c9496c8f262ab88f78927de86a4d2c2d8486 by Gilles Caulier.
Committed on 09/03/2022 at 13:11.
Pushed by cgilles into branch 'qt5-maintenance'.

AVIF in AppImage: no needs dirty libaom touch

M  +3-0project/bundles/3rdparty/ext_libavif/CMakeLists.txt
M  +0-5project/bundles/appimage/04-build-appimage.sh

https://invent.kde.org/graphics/digikam/commit/1a34c9496c8f262ab88f78927de86a4d2c2d8486

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #38 from [email protected] ---
libaom disapear from AVIF qt plugin :

[root@localhost tools (qt5-maintenance)]# ldd
/usr/plugins/imageformats/kimg_avif.so
linux-vdso.so.1 (0x7ffdeb1b2000)
libQt5Gui.so.5 => /lib/libQt5Gui.so.5 (0x7fa51e5a5000)
libavif.so.13 => /lib64/libavif.so.13 (0x7fa51df6a000)
libQt5Core.so.5 => /lib/libQt5Core.so.5 (0x7fa51d96f000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x7fa51d7e9000)
libm.so.6 => /lib64/libm.so.6 (0x7fa51d6a7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fa51d68d000)
libc.so.6 => /lib64/libc.so.6 (0x7fa51d4c1000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7fa51d4a)
libGL.so.1 => /lib64/libGL.so.1 (0x7fa51d43)
libicui18n.so.63 => /lib64/libicui18n.so.63 (0x7fa51d168000)
libicuuc.so.63 => /lib64/libicuuc.so.63 (0x7fa51cf9f000)
libicudata.so.63 => /lib64/libicudata.so.63 (0x7fa51cf9c000)
libdl.so.2 => /lib64/libdl.so.2 (0x7fa51cf95000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x7fa51cef8000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x7fa51cef3000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x7fa51cdd4000)
/lib64/ld-linux-x86-64.so.2 (0x7fa51ec7e000)
libglapi.so.0 => /lib64/libglapi.so.0 (0x7fa51cd9b000)
libdrm.so.2 => /lib64/libdrm.so.2 (0x7fa51cd87000)
libX11.so.6 => /lib64/libX11.so.6 (0x7fa51cc47000)
libxcb-glx.so.0 => /lib64/libxcb-glx.so.0 (0x7fa51cc2c000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x7fa51cc04000)
libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x7fa51cbff000)
libxcb-dri2.so.0 => /lib64/libxcb-dri2.so.0 (0x7fa51cbf9000)
libXext.so.6 => /lib64/libXext.so.6 (0x7fa51cbe5000)
libXfixes.so.3 => /lib64/libXfixes.so.3 (0x7fa51cbdb000)
libXdamage.so.1 => /lib64/libXdamage.so.1 (0x7fa51cbd6000)
libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x7fa51cbcf000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x7fa51cb93000)
libxcb-dri3.so.0 => /lib64/libxcb-dri3.so.0 (0x7fa51cb8d000)
libxcb-present.so.0 => /lib64/libxcb-present.so.0 (0x7fa51cb88000)
libxcb-sync.so.1 => /lib64/libxcb-sync.so.1 (0x7fa51cb7d000)
libxshmfence.so.1 => /lib64/libxshmfence.so.1 (0x7fa51cb78000)
libxcb-xfixes.so.0 => /lib64/libxcb-xfixes.so.0 (0x7fa51cb6f000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7fa51cafd000)
libXau.so.6 => /lib64/libXau.so.6 (0x7fa51caf8000)
libXdmcp.so.6 => /lib64/libXdmcp.so.6 (0x7fa51caee000)
libbsd.so.0 => /lib64/libbsd.so.0 (0x7fa51cad5000)
librt.so.1 => /lib64/librt.so.1 (0x7fa51caca000)
[root@localhost tools (qt5-maintenance)]#

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #37 from [email protected] ---
Et voilà :

[  0%] Creating directories for 'libaom'
[  0%] Performing download step (git clone) for 'libaom'
Clonage dans 'libaom'...
HEAD est maintenant sur 87460cef8 Replace AOM_EXT_PART_ABI_VERSION with old
value
[ 33%] No update step for 'libaom'
[ 33%] No patch step for 'libaom'
[ 66%] Performing configure step for 'libaom'
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/bin/git (found version "2.21.4") 
-- Found Perl: /usr/bin/perl (found version "5.28.3") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
--- aom_configure: Detected CPU: x86_64
Running C compiler test: inline_check_1
-- Performing Test C_TEST_COMPILED
-- Performing Test C_TEST_COMPILED - Success
Running CXX compiler test: inline_check_1
-- Performing Test CXX_TEST_COMPILED
-- Performing Test CXX_TEST_COMPILED - Success
Running C compiler test: unistd_check
-- Performing Test C_TEST_COMPILED
-- Performing Test C_TEST_COMPILED - Success
Running CXX compiler test: unistd_check
-- Performing Test CXX_TEST_COMPILED
-- Performing Test CXX_TEST_COMPILED - Success
Running C compiler test: fenv_check
-- Performing Test C_TEST_COMPILED
-- Performing Test C_TEST_COMPILED - Success
Checking C compiler flag support for: -std=c99
-- Performing Test HAVE_C_FLAG
-- Performing Test HAVE_C_FLAG - Success
Checking C compiler flag support for: -std=c++11
-- Performing Test HAVE_CXX_FLAG
-- Performing Test HAVE_CXX_FLAG - Success
Checking C compiler flag support for: -Wall
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wall
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wdisabled-optimization
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wdisabled-optimization
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wextra
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wextra
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wfloat-conversion
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wfloat-conversion
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wformat=2
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wformat=2
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wimplicit-function-declaration
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wlogical-op
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wlogical-op
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wpointer-arith
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wpointer-arith
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wshorten-64-to-32
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Failed
Checking C++ compiler flag support for: -Wshorten-64-to-32
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Failed
Checking C compiler flag support for: -Wsign-compare
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wsign-compare
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wstring-conversion
-- Performing Test C_FLAG

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #36 from [email protected] ---
Git commit dd75814d2dbefdf330d48599ae3446dda96387b6 by Gilles Caulier.
Committed on 09/03/2022 at 13:04.
Pushed by cgilles into branch 'qt5-maintenance'.

AppImage: build AOM static and AVIF as shared to prevent conflict with host
system libaom

M  +21   -3project/bundles/3rdparty/ext_libavif/CMakeLists.txt

https://invent.kde.org/graphics/digikam/commit/dd75814d2dbefdf330d48599ae3446dda96387b6

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #35 from [email protected] ---
yes, sure, the removed libaom.so.0 will certainly break ffmpeg, but, as this
lib is very old, i'm sure that loading AVIF file in ffmpeg will not work as
expected...

Rebuild ffmpeg instead to use linux appimage build host is also something that
i planned, but it's more complex cmake rules to code and test.

So the static libaom is the right way to go as a quick solution.

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #34 from [email protected] ---
(In reply to caulier.gilles from comment #32)
> An ideal solution was to build libavif with a static version of libaom...
> 
> Gilles

This is how I build static version of libaom inside libavif:
https://github.com/novomesk/qt-avif-image-plugin/blob/master/ext/build_local_libaom_libavif.sh#L32

It must be inside ext/aom/build.libavif/ folder and the -DCONFIG_PIC=1 is very
important!

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #33 from [email protected] ---
I don't know if such hack with deleting old libaom is OK. I am worried what
will happen when someone tries to play some movie with AV1 codec?

Wouldn't be better to rebuild ffmpeg so it will use the new libaom?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #32 from [email protected] ---
An ideal solution was to build libavif with a static version of libaom...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #31 from [email protected] ---
Git commit 349c15e545608403a406df47026a8a921cb74d31 by Gilles Caulier.
Committed on 09/03/2022 at 10:27.
Pushed by cgilles into branch 'qt5-maintenance'.

do not mix both libaom shared lib in the bundle

M  +5-0project/bundles/appimage/04-build-appimage.sh

https://invent.kde.org/graphics/digikam/commit/349c15e545608403a406df47026a8a921cb74d31

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #30 from [email protected] ---
If i remove libaom.so.0 from the bundle, of course it crash:

[gilles@localhost pipo]$ ./AppRun
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--to enable all debug messages on the console, use 'export
QT_LOGGING_RULES="digikam*=true"'.
Check library libudev.so.0
Check library libxcb-dri3.so.0
Check library libcrypto.so.1.1
Check library libssl.so.1.1
Check library libnss3.so
Check library libnssutil3.so
Check library libsmime3.so
-- Preloading shared libs:
:/usr/lib64/libxcb-dri3.so.0:/usr/lib64/libcrypto.so.1.1:/usr/lib64/libssl.so.1.1:/usr/lib64/libnss3.so:/usr/lib64/libnssutil3.so:/usr/lib64/libsmime3.so
digikam: error while loading shared libraries: libaom.so.0: cannot open shared
object file: No such file or directory

... but if i create a symlink like this :

ln -s libaom.so.3 libaom.so.0

digiKam starts and export to AVIF work as expected from Image Editor !!!

So if a guru can explain to me why the loader is not able to mix different
versions of a library at run-time, well i can offer a beer, because this
combination is technically possible. Or perhaps it's a limitation of AppImage,
i don't know...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #29 from [email protected] ---
When I copied these 3 files from extracted appimage:
kimg_avif.so
libavif.so.13
libaom.so.3

the plugin worked fine in gwenview.
So it works outside appimage.

Are you willing to make an experiment?

Try to build manually my plug-in from
https://github.com/novomesk/qt-avif-image-plugin
run ./build_libqavif_static.sh
It will make a local static build libqavif.so in plugins/imageformats (dav1d,
libaom, libyuv will be bundled inside)

Try to remove kimg_avif.so, libavif.so.13, libaom.so.3 and put libqavif.so into
the folder where kimg_avif.so was located.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #28 from [email protected] ---
And yes, it's ffmpeg comming from the linux host which use the older AOM lib:

[root@localhost lib64]# ldd libavformat.so.58 | grep aom
libaom.so.0 => /lib64/libaom.so.0 (0x7fbbd0e42000)

So for me no cpossible conflict at run-time, else a crash will appear as both
libaom are really different.

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #27 from [email protected] ---
libavif from the bundle point also on the right libaom version :

[root@localhost lib64]# ldd libavif.so.13 
linux-vdso.so.1 (0x7cff9000)
libaom.so.3 => /lib64/libaom.so.3 (0x7faffcfd3000)
libm.so.6 => /lib64/libm.so.6 (0x7faffce91000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7faffce7)
libc.so.6 => /lib64/libc.so.6 (0x7faffcca6000)
/lib64/ld-linux-x86-64.so.2 (0x7faffd5bb000)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #26 from [email protected] ---
yes, there are 2 libaom in the bundle. ldd help here :

[root@localhost imageformats]# ldd kimg_avif.so 
linux-vdso.so.1 (0x7ffe3a9d4000)
libQt5Gui.so.5 => /lib/libQt5Gui.so.5 (0x7fee3c115000)
libavif.so.13 => /lib64/libavif.so.13 (0x7fee3c0f5000)
libQt5Core.so.5 => /lib/libQt5Core.so.5 (0x7fee3bafa000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x7fee3b974000)
libm.so.6 => /lib64/libm.so.6 (0x7fee3b832000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fee3b818000)
libc.so.6 => /lib64/libc.so.6 (0x7fee3b64c000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7fee3b62b000)
libGL.so.1 => /lib64/libGL.so.1 (0x7fee3b5bb000)
libaom.so.3 => /lib64/libaom.so.3 (0x7fee3b019000)
libicui18n.so.63 => /lib64/libicui18n.so.63 (0x7fee3ad51000)
libicuuc.so.63 => /lib64/libicuuc.so.63 (0x7fee3ab88000)
libicudata.so.63 => /lib64/libicudata.so.63 (0x7fee3ab83000)
libdl.so.2 => /lib64/libdl.so.2 (0x7fee3ab7e000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x7fee3aae1000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x7fee3aadc000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x7fee3a9bd000)
/lib64/ld-linux-x86-64.so.2 (0x7fee3c7ee000)
libglapi.so.0 => /lib64/libglapi.so.0 (0x7fee3a984000)
libdrm.so.2 => /lib64/libdrm.so.2 (0x7fee3a96e000)
libX11.so.6 => /lib64/libX11.so.6 (0x7fee3a83)
libxcb-glx.so.0 => /lib64/libxcb-glx.so.0 (0x7fee3a815000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x7fee3a7ed000)
libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x7fee3a7e8000)
libxcb-dri2.so.0 => /lib64/libxcb-dri2.so.0 (0x7fee3a7e2000)
libXext.so.6 => /lib64/libXext.so.6 (0x7fee3a7cc000)
libXfixes.so.3 => /lib64/libXfixes.so.3 (0x7fee3a7c4000)
libXdamage.so.1 => /lib64/libXdamage.so.1 (0x7fee3a7bf000)
libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x7fee3a7b8000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x7fee3a77c000)
libxcb-dri3.so.0 => /lib64/libxcb-dri3.so.0 (0x7fee3a776000)
libxcb-present.so.0 => /lib64/libxcb-present.so.0 (0x7fee3a76f000)
libxcb-sync.so.1 => /lib64/libxcb-sync.so.1 (0x7fee3a766000)
libxshmfence.so.1 => /lib64/libxshmfence.so.1 (0x7fee3a761000)
libxcb-xfixes.so.0 => /lib64/libxcb-xfixes.so.0 (0x7fee3a758000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7fee3a6e6000)
libXau.so.6 => /lib64/libXau.so.6 (0x7fee3a6df000)
libXdmcp.so.6 => /lib64/libXdmcp.so.6 (0x7fee3a6d7000)
libbsd.so.0 => /lib64/libbsd.so.0 (0x7fee3a6be000)
librt.so.1 => /lib64/librt.so.1 (0x7fee3a6b3000)

So the KImageFormats AVIF plugin point on the right version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #25 from [email protected] ---
I don't know the real cause but I observed that inside
digiKam-7.7.0-20220308T173410-x86-64.appimage there are two versions of libaom:
libaom.so.0 (this is probably very old version 1.0.0 used by libavcodec.so.58)
libaom.so.3 (this is libaom 3.3.0)

I am not sure whether there is some conflict with different libaom versions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #24 from [email protected] ---
Hi dnovomesky

So where is the problem under Linux AppImage. I'm lost...

How to turn on the  qWarning() messages from KF5 framework. I tried all i know,
but nothing work...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #23 from [email protected] ---
Compilation trace of KImageFormats for AppImage with AVIF support:

-- extracting...
 src='/d/kimageformats-5.90.0.tar.xz'
 dst='/b/ext_kf5_frameworks/ext_kimageformats-prefix/src/ext_kimageformats'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[  0%] No update step for 'ext_kimageformats'
[  0%] No patch step for 'ext_kimageformats'
[  0%] Performing configure step for 'ext_kimageformats'
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- 

-- Installing in the same prefix as Qt, adopting their path scheme.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE
-- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success
fatal: ni ceci ni aucun de ses répertoires parents n'est un dépôt git : .git
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.6.1") 
-- Found OpenEXR: /usr/lib64/libIlmImf.so (found version "2.3.0") 
-- Checking for module 'libjxl>=0.6.1'
--   Found libjxl, version 0.6.1
-- Checking for module 'libjxl_threads>=0.6.1'
--   Found libjxl_threads, version 0.6.1
-- The following features have been enabled:

 * LibJXL, required for the QImage plugin for JPEG XL images

-- The following OPTIONAL packages have been found:

 * Qt5Core (required version >= 5.15.2)
 * KF5Archive
   Required for the QImage plugin for Krita and OpenRaster images
 * Qt5Widgets (required version >= 5.15.3)
 * Qt5PrintSupport (required version >= 5.15.2)
   Required for the QImage plugin for EPS images
 * OpenEXR, A library for handling OpenEXR high dynamic-range image files,

   Required for the QImage plugin for OpenEXR images
 * libavif (required version >= 0.8.2)
   Required for the QImage plugin for AVIF images

-- The following REQUIRED packages have been found:

 * ECM (required version >= 5.90.0), Extra CMake Modules.,

 * Qt5Gui (required version >= 5.15.2)

-- The following features have been disabled:

 * LibHeif, required for the QImage plugin for HEIF/HEIC images

-- Configuring done
-- Generating done
-- Build files have been written to:
/b/ext_kf5_frameworks/ext_kimageformats-prefix/src/ext_kimageformats-build
[  0%] Performing build step for 'ext_kimageformats'
[  3%] Automatic MOC for target kimg_hdr
[  5%] Automatic MOC for target kimg_ani
[  5%] Automatic MOC for target kimg_jxl
[  6%] Automatic MOC for target kimg_eps
[  6%] Built target kimg_hdr_autogen
[  6%] Built target kimg_ani_autogen
[  6%] Built target kimg_eps_autogen
[  8%] Automatic MOC for target kimg_avif
[ 10%] Automatic MOC for target kimg_pcx
[ 11%] Built target kimg_jxl_autogen
[ 11%] Automatic MOC for target kimg_pic
[ 13%] Automatic MOC for target kimg_psd
[ 13%] Built target kimg_avif_autogen
[ 13%] Built target kimg_pic_autogen
[ 15%] Automatic MOC for target kimg_ras
[ 15%] Built target kimg_psd_autogen
[ 16%] Automatic MOC for target kimg_exr
[ 16%] Built target kimg_pcx_autogen
[ 18%] Automatic MOC for target kimg_rgb
[ 20%] Automatic MOC for target kimg_tga
[ 20%] Built target kimg_ras_autogen
[ 21%] Automatic MOC for target kimg_kra
[ 21%] Built target kimg_rgb_autogen
[ 21%] Built target kimg_exr_autogen
[ 25%] Automatic MOC for target kimg_xcf
[ 25%] Automatic MOC for target kimg_ora
[ 25%] Built target kimg_tga_autogen
[ 26%] Building CXX object
src/imageformats/CMakeFiles/kimg_jxl.dir/kimg_jxl_autogen/mocs_compilation.cpp.o
[ 26%] Built target kimg_kra_autogen
[ 28%] Building CXX object
src/imageformats/CMakeFiles/kimg_hdr.dir/kimg_hdr_autogen/mocs_compilation.cpp.o
[ 28%] Built target kimg_xcf_autogen
[ 28%] Built target kimg_ora_autogen
[ 30%] Building CXX object src/imageformats/CMakeFiles/kimg_hdr.dir/hdr.cpp.o
[ 31%] Building CXX object
src/imageformats/CMakeFiles/kimg_eps.dir/kimg_eps_autogen/mocs_compilation.cpp.o
[ 33%] Building CXX object src/imageformats/CMakeFiles/kimg_eps.dir/eps.cpp.o
[ 35%] Building CXX object
src/imageformats/CMakeFiles/kimg_ani.dir/kimg_ani_autogen/mocs_compilation.cpp.o
[ 36%] Building CXX object src/imageformats/CMakeFiles/kimg_jxl.dir/jxl.cpp.o
[ 38%] Linking CXX shared module ../../bin/imageformats/kimg_hdr.so
[ 38%] Built target kimg_hdr
[ 40%] Building CXX object
src/imagefo

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #22 from [email protected] ---
I tried
digiKam-7.7.0-20220308T170030-Win64-debug.exe

Opening and saving AVIF works, I just had to add avif into the list of
Additional image file extensions.

libyuv is indeed optional, it can accelerate decoding process.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #21 from [email protected] ---
compilation trace of libaom and libavif under Linux for AppImage :

[  0%] Creating directories for 'libaom'
[  0%] Performing download step (git clone) for 'libaom'
Clonage dans 'libaom'...
HEAD est maintenant sur 87460cef8 Replace AOM_EXT_PART_ABI_VERSION with old
value
[ 33%] No update step for 'libaom'
[ 33%] No patch step for 'libaom'
[ 66%] Performing configure step for 'libaom'
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/bin/git (found version "2.21.4") 
-- Found Perl: /usr/bin/perl (found version "5.28.3") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
--- aom_configure: Detected CPU: x86_64
Running C compiler test: inline_check_1
-- Performing Test C_TEST_COMPILED
-- Performing Test C_TEST_COMPILED - Success
Running CXX compiler test: inline_check_1
-- Performing Test CXX_TEST_COMPILED
-- Performing Test CXX_TEST_COMPILED - Success
Running C compiler test: unistd_check
-- Performing Test C_TEST_COMPILED
-- Performing Test C_TEST_COMPILED - Success
Running CXX compiler test: unistd_check
-- Performing Test CXX_TEST_COMPILED
-- Performing Test CXX_TEST_COMPILED - Success
Running C compiler test: fenv_check
-- Performing Test C_TEST_COMPILED
-- Performing Test C_TEST_COMPILED - Success
Checking C compiler flag support for: -std=c99
-- Performing Test HAVE_C_FLAG
-- Performing Test HAVE_C_FLAG - Success
Checking C compiler flag support for: -std=c++11
-- Performing Test HAVE_CXX_FLAG
-- Performing Test HAVE_CXX_FLAG - Success
Checking C compiler flag support for: -Wall
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wall
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wdisabled-optimization
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wdisabled-optimization
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wextra
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wextra
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wfloat-conversion
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wfloat-conversion
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wformat=2
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wformat=2
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wimplicit-function-declaration
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wlogical-op
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wlogical-op
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wpointer-arith
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wpointer-arith
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag support for: -Wshorten-64-to-32
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Failed
Checking C++ compiler flag support for: -Wshorten-64-to-32
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Failed
Checking C compiler flag support for: -Wsign-compare
-- Performing Test C_FLAG_SUPPORTED
-- Performing Test C_FLAG_SUPPORTED - Success
Checking C++ compiler flag support for: -Wsign-compare
-- Performing Test CXX_FLAG_SUPPORTED
-- Performing Test CXX_FLAG_SUPPORTED - Success
Checking C compiler flag su

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #20 from [email protected] ---
AVIF support under MacOS : https://i.imgur.com/BMUti4B.png

All work as expected, expected the thumbnails, as under Windows

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #19 from [email protected] ---
But... there are qwarning() in AVIF plugin from KImageFormats :

https://invent.kde.org/frameworks/kimageformats/-/blob/master/src/imageformats/avif.cpp#L423

So...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #18 from [email protected] ---
I turned on all KF5 framework debug spaces : no warning/error
I tried all to enable all Qt debug trace : nothing special...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #17 from [email protected] ---
For AppImage Linux, AVIF export from JPEG inside Image Editor do not work :

Digikam::EditorWindow::startingSaveAs: startSavingAs called
Digikam::EditorWindow::showFileSaveDialog: Writing file to 
QUrl("file:///home/gilles/Images/SALAGOU/DSC08843.avif")
Digikam::FileSaveOptionsBox::discoverFormat: Trying to discover format based on
filename ' "DSC08843.avif" ', fallback =  0
Digikam::FileSaveOptionsBox::discoverFormat: Using fallback format  0
Digikam::FileSaveOptionsBox::discoverFormat: Discovered format:  0
Digikam::EditorWindow::selectValidSavingFormat: Trying to find a saving format
from targetUrl =  QUrl("file:///home/gilles/Images/SALAGOU/DSC08843.avif")
Digikam::EditorWindow::selectValidSavingFormat: Qt Offered types:  "*.avif
*.bmp *.bw *.cur *.eps *.epsf *.epsi *.icns *.ico *.jxl *.pbm *.pcx *.pgm *.pic
*.png *.ppm *.rgb *.rgba *.sgi *.tga *.wbmp *.webp *.xbm *.xpm *.tiff *.tif
*.jpg *.jpeg *.jpe *.jp2 *.j2k *.jpx *.pgx *.pgf *.heic *.heif *.fts *.fit
*.fits "
Digikam::EditorWindow::selectValidSavingFormat: Writable formats:  ("avif",
"bmp", "bw", "cur", "eps", "epsf", "epsi", "icns", "ico", "jxl", "pbm", "pcx",
"pgm", "pic", "png", "ppm", "rgb", "rgba", "sgi", "tga", "wbmp", "webp", "xbm",
"xpm", "tiff", "tif", "jpg", "jpeg", "jpe", "jp2", "j2k", "jpx", "pgx", "pgf",
"heic", "heif", "fts", "fit", "fits")
Digikam::EditorWindow::selectValidSavingFormat: Possible format from local
file:  "avif"
Digikam::EditorWindow::selectValidSavingFormat: Using format from target url 
"avif"
Digikam::ItemMarkerTiler::slotSourceModelReset: 
Digikam::EditorCore::Private::saveAs: Saving to :
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif" ( "avif"
)
Digikam::EditorCore::Private::saveNext: Saving file
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif" at -1
Digikam::DImg::prepareMetadataToSave: Prepare Metadata to save for
"/home/gilles/Images/SALAGOU/DSC08843.avif"
Digikam::MetaEngine::setItemPreview: JPEG image preview size: ( 1280 x 853 )
pixels - 104312 bytes
Digikam::DImg::save: Saving to 
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif"  with
format:  "avif"
Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot load metadata
from file with Exiv2 backend:
/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif  (Error #
20 :  "Failed to read input data"
Digikam::DMetadata::loadUsingImageMagick: Cannot parse metadata from [
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif" ] with
ImageMagick identify
Digikam::DMetadata::load: Loading metadata with "ImageMagick" backend from
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif"
Digikam::MetaEngine::save: MetaEngine::metadataWritingMode 0
Digikam::MetaEngine::save: Will write Metadata to file
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif"
Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot save metadata to
image with Exiv2 backend:  (Error # 20 :  "Failed to read input data"
Digikam::EditorCore::slotImageSaved: error saving image '
/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif
Digikam::EditorWindow::slotSavingFinished:
"/home/gilles/Images/SALAGOU/EditorWindow-LnKmvC.digikamtempfile.avif" false
true

Not idea why ...

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #16 from [email protected] ---
Maik, 

AVIF/AOM image thumbnail is broken, but preview work fine. I think it's due to
file format detection as video file

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #15 from [email protected] ---
AVIF/AOM support under Windows : https://i.imgur.com/KhNhNLt.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #14 from [email protected] ---
@dnovomesky

All 7.7.0-pre-release bundles compile currently with AVIF/AOM support. They
will be available in few hours for testing at usual place.

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #13 from [email protected] ---
Git commit 57b05919f7679e7ce4f5bc9437fbfebb33b0c928 by Gilles Caulier.
Committed on 08/03/2022 at 17:49.
Pushed by cgilles into branch 'master'.

AVIF support: sync with qt5-maintenance branch

M  +2-0core/libs/database/coredb/coredbschemaupdater.cpp
M  +1-0project/bundles/3rdparty/CMakeLists.txt
A  +155  -0project/bundles/3rdparty/ext_libavif/CMakeLists.txt
M  +2-0project/bundles/appimage/01-build-host.sh
M  +2-0project/bundles/macports/01-build-macports.sh
M  +1-0project/bundles/mxe/01-build-mxe.sh

https://invent.kde.org/graphics/digikam/commit/57b05919f7679e7ce4f5bc9437fbfebb33b0c928

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #12 from [email protected] ---
Git commit 8a40ecd93608acba9fdf553ec2c8d9b3d6921bf0 by Gilles Caulier.
Committed on 08/03/2022 at 17:42.
Pushed by cgilles into branch 'qt5-maintenance'.

AVIF supports under MacOS: install libaom with Macports and compile libavif

M  +1-25   project/bundles/3rdparty/ext_libavif/CMakeLists.txt
D  +0-75   project/bundles/3rdparty/ext_libavif/jxl-lib-macports.patch
M  +1-0project/bundles/macports/01-build-macports.sh

https://invent.kde.org/graphics/digikam/commit/8a40ecd93608acba9fdf553ec2c8d9b3d6921bf0

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #11 from [email protected] ---
Git commit 59e7d811308acfac5f74a8b4988f77290920f206 by Gilles Caulier.
Committed on 08/03/2022 at 17:29.
Pushed by cgilles into branch 'qt5-maintenance'.

libavif for AppImage: inst ayasm and fix compilation of aom and avif libraries

M  +3-13   project/bundles/3rdparty/ext_libavif/CMakeLists.txt
D  +0-60   project/bundles/3rdparty/ext_libavif/jxl-lib-linux.patch
D  +0-60   project/bundles/3rdparty/ext_libavif/jxl-lib-mxe.patch
M  +1-0project/bundles/appimage/01-build-host.sh

https://invent.kde.org/graphics/digikam/commit/59e7d811308acfac5f74a8b4988f77290920f206

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #10 from [email protected] ---
Git commit 2d9a589e74866b7574e4b90cdcd5d7b7c3c90952 by Gilles Caulier.
Committed on 08/03/2022 at 17:05.
Pushed by cgilles into branch 'qt5-maintenance'.

Add libaom dependency for AppImage

M  +41   -2project/bundles/3rdparty/ext_libavif/CMakeLists.txt

https://invent.kde.org/graphics/digikam/commit/2d9a589e74866b7574e4b90cdcd5d7b7c3c90952

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #9 from [email protected] ---
Git commit 82ef9588282ab4c0d9f9486cc7d7aa4580ef323a by Gilles Caulier.
Committed on 08/03/2022 at 16:57.
Pushed by cgilles into branch 'qt5-maintenance'.

add AVIF as supported type mime.

M  +1-0core/libs/database/coredb/coredbschemaupdater.cpp

https://invent.kde.org/graphics/digikam/commit/82ef9588282ab4c0d9f9486cc7d7aa4580ef323a

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #8 from [email protected] ---
Git commit 0d60eb0eb6edeb1b023facd81f5cfd3e08d9b914 by Gilles Caulier.
Committed on 08/03/2022 at 16:50.
Pushed by cgilles into branch 'qt5-maintenance'.

Fix compilation of libaom and libavif with MXE.

M  +2-2project/bundles/3rdparty/ext_libavif/CMakeLists.txt

https://invent.kde.org/graphics/digikam/commit/0d60eb0eb6edeb1b023facd81f5cfd3e08d9b914

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #7 from [email protected] ---
Git commit dbb98ebb5857f34d0c1f17f1c90a6b54189b3d35 by Gilles Caulier.
Committed on 08/03/2022 at 16:30.
Pushed by cgilles into branch 'qt5-maintenance'.

add liaom deps under MXE

M  +35   -3project/bundles/3rdparty/ext_libavif/CMakeLists.txt

https://invent.kde.org/graphics/digikam/commit/dbb98ebb5857f34d0c1f17f1c90a6b54189b3d35

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #6 from [email protected] ---
Perl must be available everywhere :

MXE (cross-compiling for Windows) -> it's a Linux host...
Macports -> MacOS VM -> ok
AppImage -> Linux of course
Snap CD -> Linux
FlatPak - Linux
Windows native CD -> I don't know, but possible

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

--- Comment #5 from [email protected] ---
Some notes regarding libaom (AV1 decoder+encoder used by libavif):

It needs Perl to build.

For optimal performance on x86_64 platform it needs assembler nasm or yasm.

libaom can be built without assembler (cmake -DAOM_TARGET_CPU=generic) but
write performance will be very slow.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 109060] Add AVIF file format support to all bundles (AppImage, MacOS, Windows)

2022-03-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109060

[email protected] changed:

   What|Removed |Added

Summary|Add support to AVIF file|Add AVIF file format
   |format to all bundles   |support to all bundles
   |(AppImage, MacOS, Windows)  |(AppImage, MacOS, Windows)

-- 
You are receiving this mail because:
You are watching all bug changes.