Open ellenjohnson opened 2 months ago
I think there was a problem with 1.18.x where tests that required the uncompressed codec were enabled even if the uncompressed codec was not enabled. The failures are harmless, but you can turn on that codec to address the problem.
The "encode" test does very basic encoding with HEVC and AV1. I'm pretty sure it is simply a wrongly set plugin path. With v1.19.x this should now be pretty automatic. I.e. when you run the tests from the build directory, it should set the plugin path automatically. If the matching encoders are not compiled, the tests are now skipped (it will report so).
Hello! On Linux, I'm building libheif v1.18.0 with libde265 as a dynamic plugin:
WITH_LIBDE265:BOOL=ON WITH_LIBDE265_PLUGIN:BOOL=ON
The build runs fine, but the tests fail -- only two tests are run, encode and region - and they both fail similar to the descriptions in https://github.com/strukturag/libheif/issues/986 and https://github.com/strukturag/libheif/issues/965. I see solution is to set LIBHEIF_PLUGIN_PATH. Does this mean set it to the absolute path where the plugins are built during the build process, meaning libheif/plugins which contains (amongst the decoder/coder c files) the libheif-libde265.so? Or the absolute path to the location of the libde265.so that I built when building libde265 v1.0.15 (prior to building libheif)? When I set it to the libheif/plugins path, I get the following results (just showing results for encode test for brevity):
When I set it to the path to containing libde265.so from building libde265, I get glibc errors:
I'm not sure what I'm doing wrong here, any help is appreciated!