I got it to build. Configure options: --with-single-user --with-booby --disable-dav1d (because av1 has code written in x86 assembly). --without-vaapi --without-vdpau --without-nv --without-wintv --without-x10tv --disable-libaom (there seem to be "always inline" functions that causes problems with arm_neon.h and other files. --disable-libwebp CinGG loads fine, menus work. Audio can be loaded and played, but no sound output. This is not a CinGG error, something with the machine low-level config. Even speaker-test does not work. Alsa config seems OK, output does not go to HDMI monitor. Video (tried short 720p video) can be loaded, but as soon as you do anything CinGG is terminated with a "bus error". don't know what that is. Not CinGG I think. Hardware is 2 core Cortex A7 at 1 GHz, 1G ram, 8G flash (for OS), 500G hdd (data), swapfile 10G on hdd (and being used quite a lot). MatN On Mon, 26 Sep 2022 16:21:39 +0300 Andrew Randrianasulu <[email protected]> wrote:
пн, 26 сент. 2022 г., 15:05 mat <[email protected]>:
Hi Andrew,
What OS did you use to compile it on the Orange Pi Lite?
this is not my personal experience, I just tried to condense talk we had at linux.org.ru forum.
I think last OS mentioned there was "Arch Linux ARM" and simple addition of armv7l case in guicast/Makefile along with previous arm8l fixed predictable build failure .... fix already in cingg git
thread https://www.linux.org.ru/forum/linux-hardware/16959253?cid=16983577
I tried earlier this year to compile it on a Cortex-A7 based CPU (Allwinner A20 2 core), the Orange PI lite has the 4 core version of that. I used Debian, and it failed quickly.
you can try again with this reported config
./configure \ --prefix=/usr \ --disable-libaom \ --disable-libwebp \ --disable-dav1d \ --disable-static-build \ --without-nv \ --without-cuda \ --with-exec-name=cinelerra-gg
and/or disable thirdparty build completely
for speeding up test compile in guicast and
cinelerra dirs
MatN