Oleg
Oleg
@igorpecovnik are there any plans to add support for TV boxes ?
> No plans. No one forbids the user to work in this direction, but what is the point of this PR for the master version?
Building armhf on aarch64 is not a cross-compilation, it is a native build. She doesn't need any checks. This is confirmed by the practice of assembling 32-bit (armhf) images on...
IMHO At this stage, I propose to limit the assembly (support) of the header only in the mode of the central Armbian server (x86). These headers will be presented (posted)...
> Но я против того, чтобы в каком либо варианте выбора собирались ломаные пакеты. >Лучше вообще не собирать ломаный пакет. можно отключить их сборку вообще, для всех хост, отличных от...
Еще нюанс, для 64 битных моделей устройств, может использоваться не только aarch64 версия образа\ядра, но и образы\ядро 32 бита, такие образы и ядро часто собирают пользователи сами на своих устройствах...
> I sincerely think that in cross compilation scenarios we can just simply disable the _kernel-headers_ packaging (only!), and simply don't output it, but indeed build everything else normally. (Also,...
By the way, I noticed another oddity, the difference between the resulting image on x86 and aarch64. When assembling on x86, in the resulting image, the bottsplash works correctly (there...
> I encountered similar problem, but I had not made the connection you did with the build host, thanks. Will investigate. @rpardini I think I figured out why the bootsplash...
I found the reason, the binary utility is being called incorrectly. It is designed for x86. :) https://github.com/armbian/build/blob/master/lib/general.sh#L701