Don't use bundled Wayland libraries when running on Wayland but use it
otherwise to satisfy possibly unsatisfied dependencies.
See also previous commit - Wayland libraries seem not to be portable and
prevent SDL2 native run on Wayland. After this change, SDL2 runs on
U22.04 in Weston (without Xwayland).
Beware not to add --whitelist=/tmp[something] because that would hide
the actual mounted image (/tmp/.mount_ultragridsomething). As /tmp is
remounted RO, just make the "whitelisted" dirs RW.
+ add to whitelist $DIR (path to executable) if it is not /tmp (eg.
extracted AppImage somewhere)
Do not interfere with UltraGrid -m parameter -- show man if only 1-2
parameters given (`uv -m 1500` doesn't make much sense for UG),
otherwise pass it to UltraGrid.
This allows using commands like `UltraGrid-continuous-x86_64.AppImage -m
1316 -t testcard -d gl` (`-m` MTU parameter at the first place).
tput returns non-zero if TERM is not set (eg. run by the CI check) and
shell is set to errexit (-e). (Previously the return value was hidden by
return value of calling echo).
This reverts commit e687bd35ac.
This currently cause following error on Arch:
expr: symbol lookup error: /lib/libva-wayland.so.2: undefined symbol: wl_proxy_marshal_flags
id: symbol lookup error: /lib/libva-wayland.so.2: undefined symbol: wl_proxy_marshal_flags
This effectively reverts 3c9b8293.
libjack.so.0 is a dependency also for different modules like portaudio
so if we do not want to depend on instance in the system, we must ship
our version.
In the second iteration of for cycle, $NAME was derived from something
like "/usr/lib/libva.so.2:/usr/lib/libva-drm.so.2" (s/libva/libva-x11),
which obviously didn't exist as a file.
Fixes:
$ <AppImage> --list-modules | grep -A 2 'Errors:'
Errors:
ultragrid_acompress_libavcodec.so
./squashfs-root2/usr/lib/libva-x11.so.2: undefined symbol: va_fool_postp
Fixed 8e77dab6f
If no pattern was found, actually whole line was printed and
whitelisted, sample wrong input:
UltraGrid-continuous-x86_64.AppImage -t testcard
Increased suggested update interval to 30 for continuous and 90 for
release - the original interval is of course advisable but 7 days for
continuous is a bit intrusive. Consequently scaling also release update
interval.
