https://bugs.kde.org/show_bug.cgi?id=448681
--- Comment #16 from caulier.gil...@gmail.com --- Hi Maik, But CAPI is used with 3 dependencies : libass, vaapi, and EGL. I don't think QtAV C++ API will be accessed by C dependencies. It's the inverse, QtAV use C API from dependencies. I read well all compilation rules from original QtAV code, and it's clear : if capi is not present with the QtAV code at configuration time, CAPI is not used and dependencies are linked instead to use dynamic loading. - from CMake rules CAPI is optional : https://github.com/wang-bin/QtAV/blob/master/src/CMakeLists.txt#L27 - from QMake rules CAPI is mandatory : https://github.com/wang-bin/QtAV/blob/master/src/libQtAV.pro#L43 Again, what's the gain of an handmaid dynamic loading ? The loader do it very well after all. I don't understand why CAPI is used here... Gilles -- You are receiving this mail because: You are watching all bug changes.
