Linus Jahn

> I use libavif from git now, let's wait for next release. OK, I see. > libavif is not present in many Linux distributions, Qt project would need to build...

@1480c1 Qt 6.0 will have full cmake support that you can (or maybe even have to) use. Building Qt with cmake on the dev branch already works well for most...

I'm not 100%-sure whether this is an option, but since this is a plugin it's probably ok if it's not always available. This means we could require an external libaom...

I think I got the same problem after debian buster upgrade. I didn't find a solution and needed to restore the server backup with debian stretch.

there are probably other places where this is the case, can you also adjust them?

I'd like to stick to the Qt conventions as much as possible. https://wiki.qt.io/API_Design_Principles#Naming_Boolean_Getters.2C_Setters.2C_and_Properties It says: * nouns shouldn't have `is` for the getter at all, except it would be misleading....

Unfortunately I'm also no expert when it's about building for android. However we have an (outdated) script to build kaidan (we now use craft for the android builds). Maybe that...

I think you need to install it into your android toolchain (`-DCMAKE_INSTALL_PREFIX=$CUSTOM_ANDROID_TOOLCHAIN`), see https://invent.kde.org/network/kaidan/-/blob/5f9abb28050c4b5f8cf135166b156bb1cdb7cffd/utils/build-android.sh#L136

Did it work?

If everything works correctly I think `androiddeployqt` should automatically copy all linked libraries into your apk. When you manually copy `libqxmpp.so`, you probably also need to create symlinks for `libqxmpp.so.4`....