Andrew,
did I miss something?
- I
checked into GIT, the
0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch,
with the changes to
configure.ac and
Makefile.am.
- Was
there another specific patch for this? Quote="I think
we traced failure back to wrong shell used for our
configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch
*release* tarball, not git commit, so install still fails
there, even if we fixed that in git.
- I
will gladly make a new test AppImage with enabling
Vulkan, but I thought that it had to be built on a
computer that had specific hardware capabilities. Am
I wrong? or can I just add "--enable-vulkan" to the
"configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed
ffmpeg 5.1 for example outright fail to build with new vulkan
headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build
OS for new appimage have it may or may not work with different
distros ... I think only way to test is try!
You also can try to enable openvpl, and see if
it get pulled into appimage so at least it starts on system
without OneVPL installed? Mismatches still possible, with all
those moving parts ...