mirror of
https://git.yoctoproject.org/poky
synced 2026-02-20 08:29:42 +01:00
aab3b7511c
While creating and deleting files with unicode or other encodings works, it's annoying when ls and other core utils show questionmarks instead of the unicode characters. In 2019, it's quite common that users of embedded devices based on yocto need unicode support. Debugging a box with unicode encoded file names is a bit annoying when core utils from busybox don't support them. The unicode config fragment has the same config as Debian in their deb and udeb builds of version 1:1.30.1-4. If developers do not want this or other default yocto features in busybox, or optimize the configuration for size, then they likely run a completely custom configuration. Thus I think it's safe to enable unicode support by default. (From OE-Core rev: a48438422dbe64095bdb379c20428ba87e2a0e99) Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
QEMU Emulation Targets ====================== To simplify development, the build system supports building images to work with the QEMU emulator in system emulation mode. Several architectures are currently supported in 32 and 64 bit variants: * ARM (qemuarm + qemuarm64) * x86 (qemux86 + qemux86-64) * PowerPC (qemuppc only) * MIPS (qemumips + qemumips64) Use of the QEMU images is covered in the Yocto Project Reference Manual. The appropriate MACHINE variable value corresponding to the target is given in brackets.