summaryrefslogtreecommitdiff
path: root/poky/documentation
diff options
context:
space:
mode:
authorAndrew Geissler <geissonator@yahoo.com>2022-09-30 21:13:31 +0300
committerAndrew Geissler <andrew@geissonator.com>2022-10-03 05:08:14 +0300
commit87f5cff0cfca11f43851cb3d7d49dd96ced7fe03 (patch)
tree5a748b271a6f682219155ce8292ca034c1b0411c /poky/documentation
parent251ad11cced0e148ba7529369597bf1d8d851032 (diff)
downloadopenbmc-87f5cff0cfca11f43851cb3d7d49dd96ced7fe03.tar.xz
subtree updates
meta-raspberrypi: c57b464b88..45d56d82b7: Andrei Gherzan (8): linux-firmware-rpidistro: Fix wireless on Raspberry Pi 4 sdcard_image-rpi.bbclass: Move SDIMG_KERNELIMAGE definitions to their machines raspberrypi0-2w.conf: Include the RPi 0-2w dtb for all 32-bit machines rpi-base.inc: Split IMAGE_BOOT_FILES for kernel image Add support for a ARMv7 machine supporting multiple Raspberry Pi boards ci: Add raspberrypi-armv7 to the build matrix Add support for a ARMv8 machine supporting multiple Raspberry Pi boards ci: Add raspberrypi-armv8 to the build matrix Chris Blättermann (1): meta-raspberrypi: Include the device tree for Raspberry Pi CM4S Khem Raj (2): rpidistro-vlc,rpidistro-ffmpeg: Limit scope to just rpi machines layers: Add langdale to LAYERSERIES_COMPAT Vincent Davis Jr (4): raspidistro-ffmpeg: add support for building raspidistro ffmpeg rpidistro-vlc: add rpidistro VLC build (with MMAL enabled) Add support for optional selection of vlc and ffmpeg docs: add info for raspberrypi distro vlc Vinicius Aquino (1): raspberrypi-firmware: Update to 20220830 snapshot meta-openembedded: a755af4fb5..0782ea454a: Adrian Freihofer (1): networkmanager: update 1.38.0 -> 1.40.0 Alejandro Enedino Hernandez Samaniego (1): emacs: Update to version 28.2 Alex Kiernan (2): libcoap: Fix gnutls/openssl/mbedtls PACKAGECONFIG conflicts libcoap: Upgrade 4.3.0 -> 4.3.1 Alexander Kanavin (7): mozjs-91: update to 91.13.0 collectd: add a python PACKAGECONFIG, off by default zbar: disable python3 support as incompatible with py 3.11 libsigrockdecode: add python 3.11 compatibility minifi-cpp: disable python support as incompatible with python 3.11 mozjs-91: backport a python 3.11 compatibility patch mozjs-78: remove the recipe Andreas Müller (1): octave: upgrade 7.1.0 -> 7.2.0 Andrej Kozemcak (1): squid: upgrade 4.15 -> 5.7 Andres Beltran (1): Make graph dependencies optional Bernhard Messerklinger (1): libconfig-tiny-perl: add recipe Chen Qi (2): passwdqc: fix the libpasswdqc FILES setting polkit: refresh patch Frank de Brabander (1): ntp: add missing runtime dependency on libgcc for sntp Gianfranco Costamagna (1): vboxguestdrivers: upgrade 6.1.36 -> 6.1.38 Hitendra Prajapati (1): wireshark: CVE-2022-3190 Infinite loop in legacy style dissector Howard Cochran (1): ufw: Fix "could not find required binary 'iptables'" Ivan Maidanski (1): bdwgc: Fix typo in EXTRA_OECONF and remove unneeded extra CFLAGS Jan Vermaete (1): makeself: upate anonymous git access and dropped man page. Khem Raj (140): gtk+: Fix function signature of create_menu() ippool: Fix build with clang15 corosync: Upgrade to 3.1.6 dlm: Upgrade to 4.1.1 dante: Upgrade to 1.4.3 ez-ipupdate: Fix build with clang openflow: Include sys/stat.h for fchmod nautilus: Backport a patch to fix build with clang-15 mctp: Update to latest tip of trunk ypbind-mt: Upgrade to 2.7.2 packagegroup-meta-networking: Remove ypbind-mt on musl fping: Fix build with musl iscsi-initiator-utils: Upgrade to 2.1.7 radvd: Fix build on musl linux-atm: Include missing string.h memcached: Upgrade to 1.6.17 openlldp: Upgrade to 1.1.0 ettercap: Pass -D_GNU_SOURCE rdma-core: Fix build with musl openl2tp: Provide prototype for l2tp_api_rpc_check_request iscsi-initiator-utils: Avoid hardcoding sed to /usr/bin/sed toybox: Remove mount.h conflict fix libuser: Upgrade to 0.63 gnome-keyring: Upgrade to 42.1 folks: Disable LTO and implicit-function-declaration as error libgtop: Fix build with clang ot-daemon,ot-br-posix: Fix mbedtls module builds libcurses-perl: Fix main prototype in testtyp.c rasdaemon: Upgrade to 0.6.8 psqlodbc: Upgrade to 13.02.0000 soci: Fix build with clang 15 geany-plugins: Fix type error found with clang 15 nlohmann-fifo: Update to tip of trunk xfce4-dev-tools: Fix configure check for libX11 frr: Fix configure check for libreadline quagga: Fix AC_CHECK_LIB for libreadline libutempter: Upgrade to 1.2.2-alt1 libuio: Update to latest tip of trunk serial-forward: Correct typo in specifying string.h header mcelog: Upgrade to v189 fvwm: Disable int-conversion and implicit-int warnings as errors hddtemp: Add missing prototype for ata_get_powermode in sata.c nana: Include stdlib.h form exit() and abort() functions libsmi: Fix build with clang 15 ckermit: Fix build with clang linuxptp: Include string.h for strncpy() wifi-test-suite: Fix build with clang xf86-video-nouveau: Do not treat implicit-function-declaration as error android-tools: Add protoype declaration for b64_pton libio-pty-perl: Fix build on musl xrdp: Fix build with clang-15 libpwquality: Do not use fgetpwent_r on musl lmbench: Add patch to fix typo including string.h header lxdm: Fix msghdr initialization on musl zabbix: Upgrade to 6.2.2 epeg: Fix AC_CHECK_LIB for libjpeg and libexif gensio: Fix AC_CHECK_LIB for libwrap pam-plugin-ccreds: Fix AC_CHECK_LIB for libdb sblim-sfcb: Fix AC_CHECK_LIB tests for various libraries rdfind: Fix AC_CHECK_LIB for libnettle srecord: Fix AC_CHECK_LIB for gpg-error tokyocabinet: Fix AC_CHECK_LIB test functions libcereal: Do not use uniform_int_distribution<char> template raptor2: Match reutrn type from RAPTOR_ASSERT_OBJECT_POINTER_RETURN_VALUE pam-ssh-agent-auth: Fix __progname configure check daemontools: Fix build with clang15 and musl pmtools: Update patch to include string.h and function prototype for main uw-imap: Fix build with clang/musl libx86: Fix pointer typecasting in assignment obconf: Add fixes for missing function prototypes sblim-sfcc: Fix build with clang sblim-sfcb: Add missing headers file for clang/musl sanlock: Add missing prototype for mem* functions geis: Add missing prototypes to functions libgxim: Enable debug mode hplip: Upgrade to 3.22.6 scsirastools: Pass -D_LARGEFILE64_SOURCE via CFLAGS con2fbmap: Include string.h for strerror directfb-examples: Fix pthread_t assignment type uml-utilities: Add missing headers for exit and str+ functions oprofile: Fix configure check for perf_events support libmcrypt: Suppress implicit-int warnings as errors gtkperf: Define prototype for setup_appdata cyrus-sasl: Fix time.h detection logic in configure enscript: Include string.h form str* function prototypes glm: Disable clang specific warnings mg: Upgrade to 20220614 release gphoto2: Upgrade to 2.5.28 ipmiutil: Add missing headers for protypes of free/malloc/atoi cdrkit: Add missing header for function prototypes fluentbit: Drop redundant patch minifi-cpp: Disable gnu extention of strerror_r when using musl augeas: Check for __GLIBC__ to use gnu extention for strerror_r nlohmann-fifo: Disable cpp11 shuffle with clang/libc++ ipmitool: Update to 1.8.19 autofs: Backport innetgr and strerror_r musl patches linux-atm: Remove AC_CHECK_LIB for libresolv hdf5: Upgrade to 1.13.2 openldap: Fix configure check for pthread_detach libimobiledevice: Explicitly pass -D_GNU_SOURCE via cflags jq: Upgrade to latest and fix configure tests lcdproc: Fix build on non-x86 and arm architectures libsmi: Define _DEFAULT_SOURCE for timegm API tftp-hpa: Fix includes for bsd_signal() sblim-sfcb: Include config.h before using CONFIG_ERROR_H minifi-cpp: Disable lto. ntp: Fix check for pthread_detach netkit-telnet: Add time.h from strftime/time prototypes passwdqc: Upgrade to 2.0.2 lmbench: Fix build time tests and use the scripts/build mcpp: Fix build with clang ot-br-posix: Fix unused variable error sthttpd: Define _GNU_SOURCE if HAVE_SIGSET is set libesmtp: Enable gnu strerror_r on glibc android-tools: Use local strlcpy implementation on glibc uw-imap: Avoid programs using gets() matplotlib: Upgrade to 3.5.3 cockpit: Update to 276 geary: Fix build with clang toybox: Fix build on 32bit arches with 64bit time_t defaults libcdio: Define _LARGEFILE64_SOURCE rocksdb: Upgrade to 7.5.3 release fwupd: Upgrade to 1.8.4 luajit: Use builtin for __clear_cache on clang kexec-tools-klibc: Fix type mismatch in calls to dtb_set_initrd on mips minifi-cpp: Fix build on musl aom: Provide missing function prototypes vulkan-cts,opengl-es-cts: Upgrade to1.3.3.1 and 3.2.8 respectively python3-lxml: Delete fwupd: Fix tostring() call to not have xml_declaration param sox: Enable -D_FILE_OFFSET_BITS=64 and depend on libtool rdfind: Fix patch-fuzz warnings fwupd: Drop sqlite3 from default deps sqlite: Drop sqlite2 recipe wvstreams: Add missing dependency on boost jack: Upgrade to 1.19.21 python3-grpcio-tools: Disable clang's musttail attribute on mips fwupd: Replace python3.7 patch with upstreamed one mdio-tools,mdio-netlink: Upgrade recipes to 1.2.0 python3-requests-unixsocket: Fix override syntax Lei Maohui (5): fltk: Fix buildpaths warning. exiv2: Fix buildpaths warning. tracker-miners: Fix buildpaths warning. gexiv2: Fix buildpaths warning. mariadb: Fix buildpaths warning. Leon Anavi (24): python3-imageio: Upgrade 2.21.1 -> 2.21.2 python3-prompt-toolkit: Upgrade 3.0.30 -> 3.0.31 python3-haversine: Upgrade 2.6.0 -> 2.7.0 python3-transitions: Upgrade 0.8.11 -> 0.9.0 python3-astroid: Upgrade 2.12.5 -> 2.12.9 python3-imageio: Upgrade 2.21.2 -> 2.21.3 python3-portion: Upgrade 2.2.0 -> 2.3.0 python3-networkx: Upgrade 2.8.5 -> 2.8.6 python3-prettytable: Upgrade 3.3.0 -> 3.4.1 python3-pydantic: Upgrade 1.9.1 -> 1.10.2 python3-soupsieve: Upgrade 2.3.1 -> 2.3.2.post1 python3-awesomeversion: Upgrade 22.8.0 -> 22.9.0 python3-ujson: Upgrade 5.4.0 -> 5.5.0 python3-marshmallow: Upgrade 3.17.1 -> 3.18.0 python3-elementpath: Upgrade 3.0.1 -> 3.0.2 python3-traitlets: Upgrade 5.3.0 -> 5.4.0 python3-joblib: Upgrade 1.1.0 -> 1.2.0 python3-astroid: Upgrade 2.12.9 -> 2.12.10 python3-imageio: Upgrade 2.21.3 -> 2.22.0 python3-email-validator: Upgrade 1.2.1 -> 1.3.0 python3-termcolor: Upgrade 1.1.0 -> 2.0.1 python3-aiohttp: Upgrade 3.8.1 -> 3.8.3 python3-pytz-deprecation-shim: Runtime dependencies python3-license-expression: Upgrade 21.6.14 -> 30.0.0 Luca Boccassi (1): dbus-broker: update to v32 Markus Volk (4): pipewire: update 0.3.56 -> 0.3.57 flatbuffers: upgrade 2.0.6 -> 2.0.8 appstream-glib: fix manpage generation jansson: use cmake instead of autotools Martin Jansa (2): lvm2: use bfd even with ld-is-gold in DISTRO_FEATURES libcec: fix runtime dependencies for ${PN}-examples Ming Liu (1): libusbgx: add PACKAGECONFIG to make build predicable Mingli Yu (2): python3-pyzmq: Fix buildpaths issue python3-pyzmq: Add RDEPENDS for python3-pyzmq-ptest Naveen Saini (1): ocl-icd: add nativesdk support Ovidiu Panait (1): redis: build with USE_SYSTEMD=yes when systemd is enabled Patrick Williams (1): unifex: remove recipe Philippe Coval (3): lvgl: Add dialog-lvgl recipe as demo example pim435: Relocate sources to eclipse ot-br-posix: Add dep to ipset as used by firewall Riyaz Khan (2): sdbus-c++: Upgrade sdbus-c++ 1.1.0 to 1.2.0 sdbus-c++-tools: Upgrade sdbus-c++-tools 1.1.0 to 1.2.0 Sergio Prado (1): polkit: refresh patch to fix warning Steffen Olsen (1): postgreql: Fix pg_config not working after buildpaths patch Vincent Davis Jr (1): cglm: New recipe for cglm-0.8.5 Wang Mingyu (16): abseil-cpp: upgrade 20220623.0 -> 20220623.1 chrony: upgrade 4.2 -> 4.3 ctags: upgrade 5.9.20220821.0 -> 5.9.20220828.0 fio: upgrade 3.31 -> 3.32 libblockdev: upgrade 2.26 -> 2.27 libdev-checklib-perl: upgrade 1.14 -> 1.16 lvm2/libdevmapper: upgrade 2.03.11 -> 2.03.16 libforms: upgrade 1.2.3 -> 1.2.4 python3-astroid: upgrade 2.12.4 -> 2.12.5 python3-colorlog: upgrade 6.6.0 -> 6.7.0 python3-django: upgrade 3.2.12 -> 4.1 python3-google-api-core: upgrade 2.8.2 -> 2.10.0 python3-google-api-python-client: upgrade 2.57.0 -> 2.58.0 python3-grpcio: upgrade 1.48.0 -> 1.48.1 python3-grpcio-tools: upgrade 1.48.0 -> 1.48.1 cli11: upgrade 1.9.1 -> 2.2.0 Xu Huan (5): python3-greenlet: upgrade 1.1.2 -> 1.1.3 python3-marshmallow: upgrade 3.17.0 -> 3.17.1 python3-pyudev: upgrade 0.23.2 -> 0.24.0 python3-websocket-client: upgrade 1.3.3 -> 1.4.0 python3-xmlschema: upgrade 2.0.2 -> 2.0.3 Yi Zhao (1): tcpreplay: fix buildpaths issue Zheng Qiu (2): jq: add ptest rsyslog: update 8.2206->8.2208 hongxu (1): python3-h5py: fix wrong file driver version wangmy (78): fuse3: upgrade 3.11.0 -> 3.12.0 xfstests: upgrade 2022.08.07 -> 2022.08.21 gnome-bluetooth: upgrade 42.3 -> 42.4 libadwaita: upgrade 1.1.4 -> 1.1.5 networkmanager-openvpn: upgrade 1.8.18 -> 1.10.0 open-isns: upgrade 0.101 -> 0.102 boost-sml: upgrade 1.1.5 -> 1.1.6 ctags: upgrade 5.9.20220828.0 -> 5.9.20220904.0 hwdata: upgrade 0.361 -> 0.362 modemmanager: upgrade 1.18.10 -> 1.18.12 php: upgrade 8.1.9 -> 8.1.10 poppler: upgrade 22.08.0 -> 22.09.0 syslog-ng: upgrade 3.37.1 -> 3.38.1 libio-socket-ssl-perl: upgrade 2.074 -> 2.075 python3-aiofiles: upgrade 0.8.0 -> 22.1.0 python3-antlr4-runtime: upgrade 4.10 -> 4.11.1 python3-croniter: upgrade 1.3.5 -> 1.3.7 python3-google-api-python-client: upgrade 2.58.0 -> 2.60.0 python3-langtable: upgrade 0.0.58 -> 0.0.59 python3-oauthlib: upgrade 3.2.0 -> 3.2.1 python3-pymetno: upgrade 0.9.0 -> 0.10.0 python3-sqlalchemy: upgrade 1.4.40 -> 1.4.41 python3-twisted: upgrade 22.4.0 -> 22.8.0 python3-websocket-client: upgrade 1.4.0 -> 1.4.1 python3-xmlschema: upgrade 2.0.3 -> 2.0.4 libadwaita: upgrade 1.1.5 -> 1.2.0 bats: upgrade 1.7.0 -> 1.8.0 ctags: upgrade 5.9.20220904.0 -> 5.9.20220911.0 iceauth: upgrade 1.0.8 -> 1.0.9 iwd: upgrade 1.29 -> 1.30 libblockdev: upgrade 2.27 -> 2.28 libjcat: upgrade 0.1.11 -> 0.1.12 libpfm4: upgrade 4.11.0 -> 4.12.0 libxmlb: upgrade 0.3.9 -> 0.3.10 neon: upgrade 0.32.2 -> 0.32.4 setxkbmap: upgrade 1.3.2 -> 1.3.3 xclock: upgrade 1.0.9 -> 1.1.1 xkbutils: upgrade 1.0.4 -> 1.0.5 xlsfonts: upgrade 1.0.6 -> 1.0.7 xmag: upgrade 1.0.6 -> 1.0.7 xwud: upgrade 1.0.5 -> 1.0.6 python3-cachecontrol: upgrade 0.12.11 -> 0.12.12 python3-cantools: upgrade 37.1.2 -> 37.2.0 python3-eth-typing: upgrade 3.1.0 -> 3.2.0 python3-fasteners: upgrade 0.17.3 -> 0.18 python3-flask-socketio: upgrade 5.3.0 -> 5.3.1 python3-google-api-core: upgrade 2.10.0 -> 2.10.1 python3-google-api-python-client: upgrade 2.60.0 -> 2.61.0 python3-grpcio-tools: upgrade 1.48.1 -> 1.49.0 python3-grpcio: upgrade 1.48.1 -> 1.49.0 python3-jsonrpcserver: upgrade 5.0.8 -> 5.0.9 python3-protobuf: upgrade 4.21.5 -> 4.21.6 xfstests: upgrade 2022.08.21 -> 2022.09.04 gnome-font-viewer: upgrade 42.0 -> 43.0 tracker: upgrade 3.3.3 -> 3.4.0 yelp-xsl: upgrade 42.0 -> 42.1 dnsmasq: upgrade 2.86 -> 2.87 unbound: upgrade 1.16.2 -> 1.16.3 cairomm-1.16: upgrade 1.16.1 -> 1.16.2 ctags: upgrade 5.9.20220911.0 -> 5.9.20220925.0 libgee: upgrade 0.20.5 -> 0.20.6 libpeas: upgrade 1.32.0 -> 1.34.0 opencl-headers: upgrade 2022.05.18 -> 2022.09.23 pangomm-2.48: upgrade 2.50.0 -> 2.50.1 thrift: upgrade 0.16.0 -> 0.17.0 zabbix: upgrade 6.2.2 -> 6.2.3 python3-djangorestframework: upgrade 3.13.1 -> 3.14.0 python3-google-api-python-client: upgrade 2.61.0 -> 2.62.0 python3-google-auth: upgrade 2.11.0 -> 2.11.1 python3-grpcio-tools: upgrade 1.49.0 -> 1.49.1 python3-grpcio: upgrade 1.49.0 -> 1.49.1 python3-h11: upgrade 0.13.0 -> 0.14.0 python3-humanize: upgrade 4.3.0 -> 4.4.0 python3-langtable: upgrade 0.0.59 -> 0.0.60 python3-ldap: upgrade 3.4.2 -> 3.4.3 python3-pandas: upgrade 1.4.4 -> 1.5.0 python3-path: upgrade 16.4.0 -> 16.5.0 python3-xmlschema: upgrade 2.0.4 -> 2.1.0 zhengrq.fnst (8): python3-astroid: upgrade 2.12.2 -> 2.12.4 python3-flatbuffers: upgrade 2.0.6 -> 2.0.7 python3-flask-socketio: upgrade 5.2.0 -> 5.3.0 python3-gnupg: upgrade 0.4.9 -> 0.5.0 python3-natsort: upgrade 8.1.0 -> 8.2.0 python3-sympy: upgrade 1.10.1 -> 1.11.1 python3-pandas: upgrade 1.4.3 -> 1.4.4 python3-parsimonious: upgrade 0.9.0 -> 0.10.0 zhengruoqin (15): wolfssl: upgrade 5.4.0 -> 5.5.0 ser2net: upgrade 4.3.7 -> 4.3.8 tree: upgrade 2.0.3 -> 2.0.4 xorgxrdp: upgrade 0.2.18 -> 0.9.19 python3-zeroconf: upgrade 0.39.0 -> 0.39.1 smarty: upgrade 4.2.0 -> 4.2.1 python3-pycocotools: upgrade 2.0.4 -> 2.0.5 python3-pyproj: upgrade 3.3.1 -> 3.4.0 python3-pyzmq: upgrade 23.2.1 -> 24.0.0 python3-regex: upgrade 2022.8.17 -> 2022.9.13 python3-pyjwt: upgrade 2.4.0 -> 2.5.0 python3-pyscaffold: upgrade 4.3 -> 4.3.1 python3-pyzmq: upgrade 24.0.0 -> 24.0.1 python3-sqlparse: upgrade 0.4.2 -> 0.4.3 python3-web3: upgrade 5.30.0 -> 5.31.0 meta-security: 10fdc2b13a..824d2762f6: Armin Kuster (4): suricata: fix compile issue cryptmount: fix systemd service install update sssd to 2.7.4 update chipsec to 1.8.8 poky: 9b1db65e7d..5200799866: Alejandro Hernandez Samaniego (1): rootfs.py: dont try to list installed packages for baremetal images Alexander Kanavin (15): selftest/cases/bblayers.py: build python3-jsonschema only once oe-setup-builddir: do not suggest local.conf as a source of examples init-system-helpers: exclude experimental tags from version check ref-manual: correct the location of default configuration template dev-manual: common-tasks.rst: drop the output of 'bitbake-layers --help' common-tasks.rst: describe the layer setup tooling dev-manual: common-tasks.rst: describe the newly added layer setup and template config commands dev-manual: common-tasks.rst: rewrite the section about configuration templates github-releases: add a class that consolidates version checks meta: fix version checks in all github recipes using the github-releases class virglrenderer: use https for fetching from gitlab local.conf.sample: correct the location of public hashserv scripts/oe-setup-builddir: do not read TEMPLATECONF from templateconf.cfg rpm: update 4.18.0-rc1 -> 4.18.0-release tzdata: update to 2022d Alexandre Belloni (2): runqemu: display host uptime when starting oeqa/runtime/dnf: fix typo Andrei Gherzan (6): depmodwrapper-cross: Take into consideration kernel package name kernel.bbclass: Pass the kernel package name to depmodwrapper kernel-module-split.bbclass: Pass the kernel package name to depmodwrapper rootfs.py: Run depmod(wrapper) against each compiled kernel rootfs.py: Drop FAKEROOT support in exec function grub: Allow build on armv7ve/a with softfp Aryaman Gupta (1): bitbake: doc: bitbake-user-manual: Add definition for BB_PRESSURE_MAX variables Bob Henz (1): systemd-systemctl: Fix WantedBy processing Bruce Ashfield (11): linux-yocto/5.15: update to v5.15.63 linux-yocto/5.19: update to v5.19.5 linux-yocto/5.19: update to v5.19.7 linux-yocto/5.15: update to v5.15.65 kern-tools: fix queue processing in relative TOPDIR configurations kern-tools: allow 'y' or 'm' to avoid config audit warnings linux-yocto/5.19: update to v5.19.9 linux-yocto/5.15: update to v5.15.68 linux-yocto/5.19: cfg: fix ACPI warnings for -tiny linux-yocto/5.15: cfg: fix ACPI warnings for -tiny linux-yocto/5.19: fix gcc-11 warning Changhyeok Bae (2): iproute2: Unset CLEANBROKEN iproute2: merge .inc into .bb Changqing Li (1): parselogs.py: ignore systemd-logind warning message Chen Qi (2): shadow-securetty: allow ttyS4 for amd-snowyowl-64 useradd-example: do not use unsupported clear text password Daniel Gomez (3): rootfs-postcommands: Remove dropbear inconsistent comment gtk-icon-cache: Fix GTKIC_CMD if-else condition dropbear: Add enable-x11-forwarding PACKAGECONFIG option Daniel McGregor (2): coreutils: add openssl PACKAGECONFIG gcc: set the default target arch Denys Dmytriyenko (1): glibc-locale: explicitly remove empty dirs in ${libdir} Dmitry Baryshkov (2): linux-firmware: upgrade 20220708 -> 20220913 linux-firmware: package new Qualcomm firmware Etienne Cordonnier (2): python3: add PACKAGECONFIG[editline] opkg: add option for zstd support Fabio Estevam (1): README.hardware.md: Fix the tftp example Florin Diaconescu (1): expat: upgrade 2.4.8 -> 2.4.9 He Zhe (2): lttng-tools: Disable on qemuriscv32 lttng-tools: Disable on riscv32 Johan Korsnes (1): ref-manual: variables: document KERNEL_IMAGETYPES John Edward Broadbent (1): externalsrc: git submodule--helper list unsupported Jose Quaresma (2): bitbake: lib/bb: warning when the debug message is invalid bitbake: fetch2/crate fixup c212b0f3 loglevel Joshua Watt (2): oeqa: qemurunner: Report UNIX Epoch timestamp on login bitbake: bitbake: Fix a few more logger debug() calls Kai Kang (2): binutils: handle symlink files for gprofng binutils: another way to clear GPROFNG_ALTS for clang and musl Khem Raj (20): autoconf: Update K & R stype functions webkitgtk: Update to 2.6.37 rust: Use variable to specify extra tools to install boost: Refrain bjam from poking into host includes gobject-introspection: Do not hardcode objdump name binutils-cross-canadian: Do not package gprofng.rc webkitgtk: Fix build on 32bit arm python3-lxml: Add recipe bitbake.conf: Define TC_CXX_RUNTIME rust: Use libc++ runtime when using clang with llvm runtime glibc: Upgrade to tip of 2.36 branch binutils: Ignore CVE-2022-38126 CVE-2022-38127 inetutils: Fix remote DoS vulnerability in inetutils-telnetd curl: Add missing perl modules in ptest rdepends elfutils: Enable ptests on musl targets grub: Apply backports to fix build with clang on x86 apt: Fix type mismatches and ptest builds linux-yocto: Enable mdio for qemu gcompat: Add __getauxval wrapper needed on aarch64 ref-manual: Define TC_CXX_RUNTIME Konrad Weihmann (1): python3-idna: migrate to flit-core Kristian Amlie (1): externalsrc: Don't wipe out src dir when EXPORT_FUNCTIONS is used. Leon Anavi (1): python3-manifest.json: Add zoneinfo Markus Volk (5): squashfs-tools: build with lzo support libsdl2: update 2.0.22 -> 2.24.0 libdrm: upgrade 2.4.112 -> 2.4.113 mesa: upgrade 22.1.6 -> 22.2.0 virglrenderer: upgrade 0.9.1 -> 0.10.3 Martin Jansa (3): webkitgtk: fix gstreamer include paths libxml2: Port gentest.py to Python-3 create-pull-request: don't switch the git remote protocol to git:// Mattias Jernberg (1): bitbake: utils: Add enable_loopback_networking() Michael Opdenacker (8): bitbake: bitbake-user-manual: mention pydevshell in OE dev-manual: common-tasks.rst: refer to Python functions in BitBake manual ref-manual: features.rst: add missing default distro features ref-manual: variables.rst: remove BBPATH ref-manual: structure.rst: add reference to the contents of the build directory ref-manual: structure.rst: improve information about build/cache/ ref-manual: variables.rst: correct templateconf.cfg file name ref-manual: structure.rst: add more subsection levels Mikko Rapeli (7): u-boot: switch from append to += in SRC_URI glibc-tests: use += instead of :append go-native: switch from SRC_URI:append to SRC_URI += python3-rfc3986-validator: switch from SRC_URI:append to SRC_URI += linux-libc-headers: switch from SRC_URI:append to SRC_URI += common-tasks.rst: remove SRC_URI:append from examples kernel-dev/common.rst: remove SRC_URI:append from examples Mingli Yu (1): busybox: add devmem 128-bit support Otavio Salvador (2): bitbake: toaster: fix kirkstone version rust-hello-world: move to recipes-extended Pascal Bach (1): bitbake: fetch2/ssh.py: fix checkstatus Paulo Neves (2): watchdog: Remove unneeded tirpc dependency bitbake: fetch2: Remove unneeded conditional Pavel Zhukov (1): core-image.bbclass: Exclude openssh complementary packages Peter Bergin (1): rootfs-postcommands.bbclass: avoid moving ssh host keys if etc is writable Peter Kjellerstedt (6): cairo: Adapt the license information based on what is being built oe-setup-builddir: Correct when validation of the templates dir is run oe-setup-builddir: Simplify error handling oe-setup-builddir: Avoid shellcheck warnings oe-setup-builddir: Keep templateconf.cfg relative if $TEMPLATECONF is oe-setup-builddir: Always update templateconf.cfg Petr Vorel (1): ltp: Update list of tests not buildable on musl Richard Purdie (54): bitbake: wget: Avoid bad checksum race issues bitbake: asyncrpc/client: Fix unix domain socket chdir race issues build-appliance-image: Update to master head revision sstate: Fix sstate file mirroring checksum issue bitbake: fetch2: Ensure mirror tarballs don't enforce checksum qemu: Upgrade 7.0.0 -> 7.1.0 qemurunner: Update to match qmp changes build-appliance-image: Update to master head revision vim: Upgrade 9.0.0341 -> 9.0.0453 selftest/qemurunner: Work around possible control character contamination oetest: Drop unused variable oetest: Drop getResults usage from oeRuntimeTest oeqa/utils/decorators: Drop unused decorators oeqa/utils/decorators: Drop getResults autoconf-archive: upgrade 2022.02.11 -> 2022.09.03 ofono: upgrade 1.34 -> 2.0 ccache: upgrade 4.6.2 -> 4.6.3 btrfs-tools: upgrade 5.19 -> 5.19.1 dnf: upgrade 4.13.0 -> 4.14.0 git: upgrade 2.37.2 -> 2.37.3 ell: upgrade 0.52 -> 0.53 file: upgrade 5.42 -> 5.43 ninja: upgrade 1.11.0 -> 1.11.1 libcomps: upgrade 0.1.18 -> 0.1.19 python3-hatchling: upgrade 1.8.1 -> 1.9.0 meson: upgrade 0.63.1 -> 0.63.2 python3-idna: upgrade 3.3 -> 3.4 librepo: upgrade 1.14.4 -> 1.14.5 python3-hypothesis: upgrade 6.46.11 -> 6.54.5 python3-numpy: upgrade 1.23.2 -> 1.23.3 libdnf: upgrade 0.68.0 -> 0.69.0 python3-psutil: upgrade 5.9.1 -> 5.9.2 ffmpeg: upgrade 5.1 -> 5.1.1 repo: upgrade 2.29.1 -> 2.29.2 nghttp2: upgrade 1.48.0 -> 1.49.0 libjitterentropy: upgrade 3.4.0 -> 3.4.1 sqlite3: upgrade 3.39.2 -> 3.39.3 diffoscope: upgrade 220 -> 221 python3-certifi: upgrade 2022.6.15 -> 2022.9.14 libpng: upgrade 1.6.37 -> 1.6.38 numactl: upgrade 2.0.14 -> 2.0.15 rpm: Upgrade 4.17.1 -> 4.18rc1 perf: Fix for recent kernel upgrades oeqa/runtime/virgl: Update test to match new mesa version vim: Upgrade 9.0.453 -> 9.0.541 vim: Upgrade 9.0.0541 -> 9.0.0598 qemu: Add patch to address arm qemu upgrade issues layer.conf: Update to use langdale as the core layer name poky: Update to 4.1 version poky: Update to match poky version numbers bitbake: bitbake: Bump to version 2.2.0 build-appliance-image: Update to master head revision go: Fix reproducibility failures build-appliance-image: Update to master head revision Robert Joslyn (6): xorg-lib-common: Add variable to set tarball type libxfont2: Update 2.0.5 to 2.0.6 libxau: Update 1.0.9 to 1.0.10 libfontenc: Update 1.1.4 to 1.1.6 flac: Update 1.3.4 to 1.4.0 tzdata: Update from 2022b to 2022c Ross Burton (16): meta-selftest/poison: improve sysroot poisoning test case gcc-cross: pass -Werror=poison-system-directories to compiler stages gcc: remove obsolete 0012-export-CPP.patch xmlto: remove redundant patches tiff: backport fix for CVE-2022-2953 gcc: remove obsolete poisoned calloc workaround gcc: remove obsolete MinGW patch oeqa/selftest/debuginfod: don't re-use the database libgcrypt: disable bench-slope test case libxml2: don't override XML_CATALOG_FILES in xmllint wrapper if already set glibc: mark a CVE where we have merged the fix qemu: re-add the fix for CVE-2022-1050 qemu: fix CVE-2022-2962 dnf: add dummy packages for testing oeqa/runtime/dnf: use dnf-test packages Revert "wic/plugins/images/direct: Allow changes in fstab on rootfs" Ruiqiang Hao (1): tune-neoversen2: support tune-neoversen2 base on armv9a Samuli Piippo (2): Revert "gcc-cross-canadian: Add symlink to real-ld alongside other symlinks" gcc-cross-canadian: add default plugin linker Stefano Babic (1): libubootenv: upgrade 0.3.2 -> 0.3.3 Sundeep KOKKONDA (1): rust-cross-canadian: Fix for the issue caused by using sdk shell Teoh Jay Shen (1): bind: upgrade 9.18.6 -> 9.18.7 Tom Hochstein (2): cmake: Fix CMAKE_SYSTEM_PROCESSOR setting for SDK connman: Drop redundant nfsroot handling Ulrich Ölmann (5): icecc.bbclass: fix typos icecc.bbclass: delete 'rm' command manuals: fix paths to default templates & clean up whitespaces icecc.bbclass: fix filename of recipe in comment manuals: fix typos in the context of 'icecc' & clean up whitespaces Vyacheslav Yurkov (5): oeqa/selftest: drop image_feature test from overlayfs classes: Update overlayfs classes to use new bitbake functionality files: overlayfs-etc: refactor preinit template classes: files: Extend overlayfs-etc class oeqa/selftest: Add lower layer test for overlayfs-etc niko.mauno@vaisala.com (2): systemd: Add 'no-dns-fallback' PACKAGECONFIG option systemd: Fix unwritable /var/lock when no sysvinit handling pgowda (4): rust: Add linker configurations for cross compilation rust: Enable verbose-tests to get the test results in readable format binutils : CVE-2022-38533 binutils : Fix CVE-2022-38128 wangmy (9): cracklib: upgrade 2.9.7 -> 2.9.8 kmscube: upgrade to latest revision piglit: upgrade to latest revision python3-dtschema: upgrade 2022.8.1 -> 2022.8.3 python3-mako: upgrade 1.2.1 -> 1.2.2 python3-pathspec: upgrade 0.9.0 -> 0.10.1 python3-pytest: upgrade 7.1.2 -> 7.1.3 vala: upgrade 0.56.2 -> 0.56.3 less: upgrade 600 -> 608 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I1705b78d8a5ef5762fe770a69ed9b866fac52ccf
Diffstat (limited to 'poky/documentation')
-rw-r--r--poky/documentation/dev-manual/common-tasks.rst220
-rw-r--r--poky/documentation/kernel-dev/common.rst12
-rw-r--r--poky/documentation/overview-manual/concepts.rst4
-rw-r--r--poky/documentation/ref-manual/classes.rst15
-rw-r--r--poky/documentation/ref-manual/faq.rst7
-rw-r--r--poky/documentation/ref-manual/features.rst43
-rw-r--r--poky/documentation/ref-manual/structure.rst81
-rw-r--r--poky/documentation/ref-manual/variables.rst69
8 files changed, 254 insertions, 197 deletions
diff --git a/poky/documentation/dev-manual/common-tasks.rst b/poky/documentation/dev-manual/common-tasks.rst
index b08a55331d..559709d6f3 100644
--- a/poky/documentation/dev-manual/common-tasks.rst
+++ b/poky/documentation/dev-manual/common-tasks.rst
@@ -653,39 +653,6 @@ For help on the BitBake layer management tool, use the following
command::
$ bitbake-layers --help
- NOTE: Starting bitbake server...
- usage: bitbake-layers [-d] [-q] [-F] [--color COLOR] [-h] <subcommand> ...
-
- BitBake layers utility
-
- optional arguments:
- -d, --debug Enable debug output
- -q, --quiet Print only errors
- -F, --force Force add without recipe parse verification
- --color COLOR Colorize output (where COLOR is auto, always, never)
- -h, --help show this help message and exit
-
- subcommands:
- <subcommand>
- layerindex-fetch Fetches a layer from a layer index along with its
- dependent layers, and adds them to conf/bblayers.conf.
- layerindex-show-depends
- Find layer dependencies from layer index.
- add-layer Add one or more layers to bblayers.conf.
- remove-layer Remove one or more layers from bblayers.conf.
- flatten flatten layer configuration into a separate output
- directory.
- show-layers show current configured layers.
- show-overlayed list overlayed recipes (where the same recipe exists
- in another layer)
- show-recipes list available recipes, showing the layer they are
- provided by
- show-appends list bbappend files and recipe files they apply to
- show-cross-depends Show dependencies between recipes that cross layer
- boundaries.
- create-layer Create a basic layer
-
- Use bitbake-layers <subcommand> --help to get help on a specific command
The following list describes the available commands:
@@ -759,8 +726,18 @@ The following list describes the available commands:
- ``layerindex-show-depends``: Finds layer dependencies from the
layer index.
+- ``save-build-conf``: Saves the currently active build configuration
+ (``conf/local.conf``, ``conf/bblayers.conf``) as a template into a layer.
+ This template can later be used for setting up builds via :term:``TEMPLATECONF``.
+ For information about saving and using configuration templates, see
+ ":ref:`dev-manual/common-tasks:creating a custom template configuration directory`".
+
- ``create-layer``: Creates a basic layer.
+- ``create-layers-setup``: Writes out a configuration file and/or a script that
+ can replicate the directory structure and revisions of the layers in a current build.
+ For more information, see ":ref:`dev-manual/common-tasks:saving and restoring the layers setup`".
+
Creating a General Layer Using the ``bitbake-layers`` Script
------------------------------------------------------------
@@ -880,6 +857,62 @@ enables the build system to locate the layer during the build.
During a build, the OpenEmbedded build system looks in the layers
from the top of the list down to the bottom in that order.
+Saving and restoring the layers setup
+-------------------------------------
+
+Once you have a working build with the correct set of layers, it is beneficial
+to capture the layer setup --- what they are, which repositories they come from
+and which SCM revisions they're at --- into a configuration file, so that this
+setup can be easily replicated later, perhaps on a different machine. Here's
+how to do this::
+
+ $ bitbake-layers create-layers-setup /srv/work/alex/meta-alex/
+ NOTE: Starting bitbake server...
+ NOTE: Created /srv/work/alex/meta-alex/setup-layers.json
+ NOTE: Created /srv/work/alex/meta-alex/setup-layers
+
+The tool needs a single argument which tells where to place the output, consisting
+of a json formatted layer configuration, and a ``setup-layers`` script that can use that configuration
+to restore the layers in a different location, or on a different host machine. The argument
+can point to a custom layer (which is then deemed a "bootstrap" layer that needs to be
+checked out first), or into a completely independent location.
+
+The replication of the layers is performed by running the ``setup-layers`` script provided
+above:
+
+1. Clone the bootstrap layer or some other repository to obtain
+ the json config and the setup script that can use it.
+
+2. Run the script directly with no options::
+
+ alex@Zen2:/srv/work/alex/my-build$ meta-alex/setup-layers
+ Note: not checking out source meta-alex, use --force-bootstraplayer-checkout to override.
+
+ Setting up source meta-intel, revision 15.0-hardknott-3.3-310-g0a96edae, branch master
+ Running 'git init -q /srv/work/alex/my-build/meta-intel'
+ Running 'git remote remove origin > /dev/null 2>&1; git remote add origin git://git.yoctoproject.org/meta-intel' in /srv/work/alex/my-build/meta-intel
+ Running 'git fetch -q origin || true' in /srv/work/alex/my-build/meta-intel
+ Running 'git checkout -q 0a96edae609a3f48befac36af82cf1eed6786b4a' in /srv/work/alex/my-build/meta-intel
+
+ Setting up source poky, revision 4.1_M1-372-g55483d28f2, branch akanavin/setup-layers
+ Running 'git init -q /srv/work/alex/my-build/poky'
+ Running 'git remote remove origin > /dev/null 2>&1; git remote add origin git://git.yoctoproject.org/poky' in /srv/work/alex/my-build/poky
+ Running 'git fetch -q origin || true' in /srv/work/alex/my-build/poky
+ Running 'git remote remove poky-contrib > /dev/null 2>&1; git remote add poky-contrib ssh://git@push.yoctoproject.org/poky-contrib' in /srv/work/alex/my-build/poky
+ Running 'git fetch -q poky-contrib || true' in /srv/work/alex/my-build/poky
+ Running 'git checkout -q 11db0390b02acac1324e0f827beb0e2e3d0d1d63' in /srv/work/alex/my-build/poky
+
+.. note::
+ This will work to update an existing checkout as well.
+
+.. note::
+ The script is self-sufficient and requires only python3
+ and git on the build machine.
+
+.. note::
+ Both the ``create-layers-setup`` and the ``setup-layers`` provided several additional options
+ that customize their behavior - you are welcome to study them via ``--help`` command line parameter.
+
Customizing Images
==================
@@ -2577,7 +2610,7 @@ chapter of the BitBake User Manual.
S = "${WORKDIR}/postfix-${PV}"
CFLAGS += "-DNO_ASM"
- SRC_URI:append = " file://fixup.patch"
+ CFLAGS:append = " --enable-important-feature"
- *Functions:* Functions provide a series of actions to be performed.
You usually use functions to override the default implementation of a
@@ -2708,19 +2741,21 @@ in the BitBake User Manual.
to existing variables. This operator does not add any additional
space. Also, the operator is applied after all the ``+=``, and ``=+``
operators have been applied and after all ``=`` assignments have
- occurred.
+ occurred. This means that if ``:append`` is used in a recipe, it can
+ only be overridden by another layer using the special ``:remove``
+ operator, which in turn will prevent further layers from adding it back.
The following example shows the space being explicitly added to the
start to ensure the appended value is not merged with the existing
value::
- SRC_URI:append = " file://fix-makefile.patch"
+ CFLAGS:append = " --enable-important-feature"
You can also use
the ``:append`` operator with overrides, which results in the actions
only being performed for the specified target or machine::
- SRC_URI:append:sh4 = " file://fix-makefile.patch"
+ CFLAGS:append:sh4 = " --enable-important-sh4-specific-feature"
- *Prepending (:prepend):* Use the ``:prepend`` operator to prepend
values to existing variables. This operator does not add any
@@ -3560,6 +3595,9 @@ functions::
pydevshell> bb.build.exec_func("do_unpack", d)
pydevshell>
+See the ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:functions you can call from within python`"
+section in the BitBake User Manual for details about available functions.
+
The commands execute just as if the OpenEmbedded build
system were executing them. Consequently, working this way can be
helpful when debugging a build or preparing software to be used with the
@@ -6431,71 +6469,51 @@ Creating a Custom Template Configuration Directory
==================================================
If you are producing your own customized version of the build system for
-use by other users, you might want to customize the message shown by the
-setup script or you might want to change the template configuration
-files (i.e. ``local.conf`` and ``bblayers.conf``) that are created in a
-new build directory.
-
-The OpenEmbedded build system uses the environment variable
-:term:`TEMPLATECONF` to locate the directory from which it gathers
-configuration information that ultimately ends up in the
-:term:`Build Directory` ``conf`` directory.
-By default, :term:`TEMPLATECONF` is set as follows in the ``poky``
-repository::
+use by other users, you might want to provide a custom build configuration
+that includes all the necessary settings and layers (i.e. ``local.conf`` and
+``bblayers.conf`` that are created in a new build directory) and a custom
+message that is shown when setting up the build. This can be done by
+creating one or more template configuration directories in your
+custom distribution layer.
- TEMPLATECONF=${TEMPLATECONF:-meta-poky/conf}
+This can be done by using ``bitbake-layers save-build-conf``::
-This is the
-directory used by the build system to find templates from which to build
-some key configuration files. If you look at this directory, you will
-see the ``bblayers.conf.sample``, ``local.conf.sample``, and
-``conf-notes.txt`` files. The build system uses these files to form the
-respective ``bblayers.conf`` file, ``local.conf`` file, and display the
-list of BitBake targets when running the setup script.
-
-To override these default configuration files with configurations you
-want used within every new Build Directory, simply set the
-:term:`TEMPLATECONF` variable to your directory. The :term:`TEMPLATECONF`
-variable is set in the ``.templateconf`` file, which is in the top-level
-:term:`Source Directory` folder
-(e.g. ``poky``). Edit the ``.templateconf`` so that it can locate your
-directory.
+ $ bitbake-layers save-build-conf ../../meta-alex/ test-1
+ NOTE: Starting bitbake server...
+ NOTE: Configuration template placed into /srv/work/alex/meta-alex/conf/templates/test-1
+ Please review the files in there, and particularly provide a configuration description in /srv/work/alex/meta-alex/conf/templates/test-1/conf-notes.txt
+ You can try out the configuration with
+ TEMPLATECONF=/srv/work/alex/meta-alex/conf/templates/test-1 . /srv/work/alex/poky/oe-init-build-env build-try-test-1
-Best practices dictate that you should keep your template configuration
-directory in your custom distribution layer. For example, suppose you
-have a layer named ``meta-mylayer`` located in your home directory and
-you want your template configuration directory named ``myconf``.
-Changing the ``.templateconf`` as follows causes the OpenEmbedded build
-system to look in your directory and base its configuration files on the
-``*.sample`` configuration files it finds. The final configuration files
-(i.e. ``local.conf`` and ``bblayers.conf`` ultimately still end up in
-your Build Directory, but they are based on your ``*.sample`` files.
-::
+The above command takes the config files from the currently active build directory under ``conf``,
+replaces site-specific paths in ``bblayers.conf`` with ``##OECORE##``-relative paths, and copies
+the config files into a specified layer under a specified template name.
- TEMPLATECONF=${TEMPLATECONF:-meta-mylayer/myconf}
+To use those saved templates as a starting point for a build, users should point
+to one of them with :term:`TEMPLATECONF` environment variable::
-Aside from the ``*.sample`` configuration files, the ``conf-notes.txt``
-also resides in the default ``meta-poky/conf`` directory. The script
-that sets up the build environment (i.e.
-:ref:`structure-core-script`) uses this file to
-display BitBake targets as part of the script output. Customizing this
-``conf-notes.txt`` file is a good way to make sure your list of custom
-targets appears as part of the script's output.
+ TEMPLATECONF=/srv/work/alex/meta-alex/conf/templates/test-1 . /srv/work/alex/poky/oe-init-build-env build-try-test-1
-Here is the default list of targets displayed as a result of running
-either of the setup scripts::
+The OpenEmbedded build system uses the environment variable
+:term:`TEMPLATECONF` to locate the directory from which it gathers
+configuration information that ultimately ends up in the
+:term:`Build Directory` ``conf`` directory.
- You can now run 'bitbake <target>'
+If :term:`TEMPLATECONF` is not set, the default value is obtained
+from ``.templateconf`` file that is read from the same directory as
+``oe-init-build-env`` script. For the Poky reference distribution this
+would be::
- Common targets are:
- core-image-minimal
- core-image-sato
- meta-toolchain
- meta-ide-support
+ TEMPLATECONF=${TEMPLATECONF:-meta-poky/conf/templates/default}
-Changing the listed common targets is as easy as editing your version of
-``conf-notes.txt`` in your custom template configuration directory and
-making sure you have :term:`TEMPLATECONF` set to your directory.
+If you look at a configuration template directory, you will
+see the ``bblayers.conf.sample``, ``local.conf.sample``, and
+``conf-notes.txt`` files. The build system uses these files to form the
+respective ``bblayers.conf`` file, ``local.conf`` file, and show
+users a note about the build they're setting up
+when running the ``oe-init-build-env`` setup script. These can be
+edited further if needed to improve or change the build configurations
+available to the users.
Conserving Disk Space
=====================
@@ -11417,12 +11435,12 @@ example:
# clean up the .git repos
$ find . -name ".git" -type d -exec rm -rf {} \;
-One
-thing a development organization might want to consider for end-user
-convenience is to modify ``meta-poky/conf/bblayers.conf.sample`` to
-ensure that when the end user utilizes the released build system to
-build an image, the development organization's layers are included in
-the ``bblayers.conf`` file automatically::
+One thing a development organization might want to consider for end-user
+convenience is to modify
+``meta-poky/conf/templates/default/bblayers.conf.sample`` to ensure that when
+the end user utilizes the released build system to build an image, the
+development organization's layers are included in the ``bblayers.conf`` file
+automatically::
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
@@ -11451,9 +11469,9 @@ The spdx module has been integrated to a layer named meta-spdxscanner.
meta-spdxscanner provides several kinds of scanner. If you want to enable
this function, you have to follow the following steps:
-1. Add meta-spdxscanner layer into ``bblayers.conf``.
+1. Add meta-spdxscanner layer into ``bblayers.conf``.
-2. Refer to the README in meta-spdxscanner to setup the environment (e.g,
+2. Refer to the README in meta-spdxscanner to setup the environment (e.g,
setup a fossology server) needed for the scanner.
3. Meta-spdxscanner provides several methods within the bbclass to create spdx files.
diff --git a/poky/documentation/kernel-dev/common.rst b/poky/documentation/kernel-dev/common.rst
index 16ef6453bd..fb8d7cd029 100644
--- a/poky/documentation/kernel-dev/common.rst
+++ b/poky/documentation/kernel-dev/common.rst
@@ -360,9 +360,9 @@ home directory:
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
- SRC_URI:append = " file://patch-file-one.patch"
- SRC_URI:append = " file://patch-file-two.patch"
- SRC_URI:append = " file://patch-file-three.patch"
+ SRC_URI += "file://patch-file-one.patch"
+ SRC_URI += "file://patch-file-two.patch"
+ SRC_URI += "file://patch-file-three.patch"
The :term:`FILESEXTRAPATHS` and :term:`SRC_URI` statements
enable the OpenEmbedded build system to find patch files. For more
@@ -1002,7 +1002,7 @@ Section.
contents::
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
- SRC_URI:append = " file://0001-calibrate.c-Added-some-printk-statements.patch"
+ SRC_URI += "file://0001-calibrate.c-Added-some-printk-statements.patch"
The :term:`FILESEXTRAPATHS` and :term:`SRC_URI` statements
enable the OpenEmbedded build system to find the patch file.
@@ -1875,7 +1875,7 @@ build.
2. *Add the Feature File to SRC_URI:* Add the ``.scc`` file to the
recipe's :term:`SRC_URI` statement::
- SRC_URI:append = " file://test.scc"
+ SRC_URI += "file://test.scc"
The leading space before the path is important as the path is
appended to the existing path.
@@ -1884,7 +1884,7 @@ build.
:term:`KERNEL_FEATURES` statement to specify the feature as a kernel
feature::
- KERNEL_FEATURES:append = " test.scc"
+ KERNEL_FEATURES += "test.scc"
The OpenEmbedded build
system processes the kernel feature when it builds the kernel.
diff --git a/poky/documentation/overview-manual/concepts.rst b/poky/documentation/overview-manual/concepts.rst
index 83339da98f..8e0303f0e0 100644
--- a/poky/documentation/overview-manual/concepts.rst
+++ b/poky/documentation/overview-manual/concepts.rst
@@ -269,7 +269,7 @@ The ``local.conf`` file provides many basic variables that define a
build environment. Here is a list of a few. To see the default
configurations in a ``local.conf`` file created by the build environment
script, see the
-:yocto_git:`local.conf.sample </poky/tree/meta-poky/conf/local.conf.sample>`
+:yocto_git:`local.conf.sample </poky/tree/meta-poky/conf/templates/default/local.conf.sample>`
in the ``meta-poky`` layer:
- *Target Machine Selection:* Controlled by the
@@ -1006,7 +1006,7 @@ data files are deleted from the root filesystem. As part of the final
stage of package installation, post installation scripts that are part
of the packages are run. Any scripts that fail to run on the build host
are run on the target when the target system is first booted. If you are
-using a
+using a
:ref:`read-only root filesystem <dev-manual/common-tasks:creating a read-only root filesystem>`,
all the post installation scripts must succeed on the build host during
the package installation phase since the root filesystem on the target
diff --git a/poky/documentation/ref-manual/classes.rst b/poky/documentation/ref-manual/classes.rst
index 424c505715..11e0d472e8 100644
--- a/poky/documentation/ref-manual/classes.rst
+++ b/poky/documentation/ref-manual/classes.rst
@@ -580,8 +580,8 @@ Finally, here is an example that sets the root password::
.. note::
From a security perspective, hardcoding a default password is not
- generally a good idea or even legal in some jurisdictions. It is
- recommended that you do not do this if you are building a production
+ generally a good idea or even legal in some jurisdictions. It is
+ recommended that you do not do this if you are building a production
image.
@@ -792,7 +792,7 @@ The class stages directories with symlinks from ``gcc`` and ``g++`` to
``icecc``, for both native and cross compilers. Depending on each
configure or compile, the OpenEmbedded build system adds the directories
at the head of the ``PATH`` list and then sets the ``ICECC_CXX`` and
-``ICEC_CC`` variables, which are the paths to the ``g++`` and ``gcc``
+``ICECC_CC`` variables, which are the paths to the ``g++`` and ``gcc``
compilers, respectively.
For the cross compiler, the class creates a ``tar.gz`` file that
@@ -800,8 +800,8 @@ contains the Yocto Project toolchain and sets ``ICECC_VERSION``, which
is the version of the cross-compiler used in the cross-development
toolchain, accordingly.
-The class handles all three different compile stages (i.e native
-,cross-kernel and target) and creates the necessary environment
+The class handles all three different compile stages (i.e native,
+cross-kernel and target) and creates the necessary environment
``tar.gz`` file to be used by the remote machines. The class also
supports SDK generation.
@@ -811,12 +811,13 @@ using ``which``. If :term:`ICECC_ENV_EXEC` is set
in your ``local.conf`` file, the variable should point to the
``icecc-create-env`` script provided by the user. If you do not point to
a user-provided script, the build system uses the default script
-provided by the recipe ``icecc-create-env-native.bb``.
+provided by the recipe :oe_git:`icecc-create-env_0.1.bb
+</openembedded-core/tree/meta/recipes-devtools/icecc-create-env/icecc-create-env_0.1.bb>`.
.. note::
This script is a modified version and not the one that comes with
- icecc.
+ ``icecream``.
If you do not want the Icecream distributed compile support to apply to
specific recipes or classes, you can ask them to be ignored by Icecream
diff --git a/poky/documentation/ref-manual/faq.rst b/poky/documentation/ref-manual/faq.rst
index 2fcbf7da96..61049523a0 100644
--- a/poky/documentation/ref-manual/faq.rst
+++ b/poky/documentation/ref-manual/faq.rst
@@ -137,9 +137,10 @@ To use them, remove the comments::
#use_proxy = on
The Yocto Project also includes a
-``meta-poky/conf/site.conf.sample`` file that shows how to configure CVS
-and Git proxy servers if needed. For more information on setting up
-various proxy types and configuring proxy servers, see the
+``meta-poky/conf/templates/default/site.conf.sample`` file that shows
+how to configure CVS and Git proxy servers if needed. For more
+information on setting up various proxy types and configuring proxy
+servers, see the
":yocto_wiki:`Working Behind a Network Proxy </Working_Behind_a_Network_Proxy>`"
Wiki page.
diff --git a/poky/documentation/ref-manual/features.rst b/poky/documentation/ref-manual/features.rst
index 8dfe29d66a..5e853caa2c 100644
--- a/poky/documentation/ref-manual/features.rst
+++ b/poky/documentation/ref-manual/features.rst
@@ -113,10 +113,15 @@ configuration level. See the
information.
This list only represents features as shipped with the Yocto Project
-metadata:
+metadata, as extra layers can define their own:
-- *alsa:* Include ALSA support (OSS compatibility kernel modules
- installed if available).
+- *3g:* Include support for cellular data.
+
+- *acl:* Include
+ `Access Control List <https://en.wikipedia.org/wiki/Access-control_list>`__ support.
+
+- *alsa:* Include `Advanced Linux Sound Architecture <https://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture>`__
+ support (OSS compatibility kernel modules installed if available).
- *api-documentation:* Enables generation of API documentation during
recipe builds. The resulting documentation is added to SDK tarballs
@@ -129,6 +134,10 @@ metadata:
- *cramfs:* Include CramFS support.
+- *debuginfod:* Include support for getting ELF debugging information through
+ a :ref:`debuginfod <dev-manual/common-tasks:using the debuginfod server method>`
+ server.
+
- *directfb:* Include DirectFB support.
- *ext2:* Include tools for supporting for devices with internal
@@ -136,14 +145,25 @@ metadata:
- *ipsec:* Include IPSec support.
+- *ipv4:* Include IPv4 support.
+
- *ipv6:* Include IPv6 support.
- *keyboard:* Include keyboard support (e.g. keymaps will be loaded
during boot).
+- *largefile:* Enable building applications with
+ `argefile support <https://en.wikipedia.org/wiki/Large-file_support>`__.
+
+- *multiarch:* Enable building applications with multiple architecture
+ support.
+
- *ldconfig:* Include support for ldconfig and ``ld.so.conf`` on the
target.
+- *nfc:* Include support for
+ `Near Field Communication <https://en.wikipedia.org/wiki/Near-field_communication>`__.
+
- *nfs:* Include NFS client support (for mounting NFS exports on
device).
@@ -162,6 +182,11 @@ metadata:
":ref:`dev-manual/common-tasks:testing packages with ptest`" section
in the Yocto Project Development Tasks Manual.
+- *seccomp:* Enables building applications with
+ `seccomp <https://en.wikipedia.org/wiki/Seccomp>`__ support, to
+ allow them to strictly restrict the system calls that they are allowed
+ to invoke.
+
- *smbfs:* Include SMB networks client support (for mounting
Samba/Microsoft Windows shares on device).
@@ -180,6 +205,12 @@ metadata:
directories into their respective counterparts in the ``/usr``
directory to provide better package and application compatibility.
+- *vfat:* Include `FAT filesystem <https://en.wikipedia.org/wiki/File_Allocation_Table>`__
+ support.
+
+- *vulkan:* Include support for the
+ `Vulkan API <https://en.wikipedia.org/wiki/Vulkan>`__.
+
- *wayland:* Include the Wayland display server protocol and the
library that supports it.
@@ -187,6 +218,12 @@ metadata:
- *x11:* Include the X server and libraries.
+- *xattr:* Include support for
+ `extended file attributes <https://en.wikipedia.org/wiki/Extended_file_attributes>`__.
+
+- *zeroconf:* Include support for
+ `zero configuration networking <https://en.wikipedia.org/wiki/Zero-configuration_networking>`__.
+
.. _ref-features-image:
Image Features
diff --git a/poky/documentation/ref-manual/structure.rst b/poky/documentation/ref-manual/structure.rst
index bdcffc1947..429f81e14c 100644
--- a/poky/documentation/ref-manual/structure.rst
+++ b/poky/documentation/ref-manual/structure.rst
@@ -68,6 +68,9 @@ information on separating output from your local Source Directory files
(commonly described as an "out of tree" build), see the
":ref:`structure-core-script`" section.
+See the ":ref:`The Build Directory --- build/ <structure-build>`" section for details
+about the contents of the :term:`Build Directory`.
+
.. _handbook:
``documentation/``
@@ -189,7 +192,7 @@ Directory named ``mybuilds/`` that is outside of the :term:`Source Directory`::
$ source oe-init-build-env ~/mybuilds
The OpenEmbedded build system uses the template configuration files, which
-are found by default in the ``meta-poky/conf/`` directory in the Source
+are found by default in the ``meta-poky/conf/templates/default`` directory in the Source
Directory. See the
":ref:`dev-manual/common-tasks:creating a custom template configuration directory`"
section in the Yocto Project Development Tasks Manual for more
@@ -237,6 +240,18 @@ subdirectories. For information on the build history feature, see the
":ref:`dev-manual/common-tasks:maintaining build output quality`"
section in the Yocto Project Development Tasks Manual.
+.. _structure-build-cache:
+
+``build/cache/``
+----------------
+
+This directory contains several internal files used by the OpenEmbedded
+build system.
+
+It also contains ``sanity_info``, a text file keeping track of important
+build information such as the values of :term:`TMPDIR`, :term:`SSTATE_DIR`,
+as well as the name and version of the host distribution.
+
.. _structure-build-conf-local.conf:
``build/conf/local.conf``
@@ -261,15 +276,15 @@ OpenEmbedded build system creates it from ``local.conf.sample`` when you
:ref:`structure-core-script`.
The source ``local.conf.sample`` file used depends on the
-:term:`TEMPLATECONF` script variable, which defaults to ``meta-poky/conf/``
+:term:`TEMPLATECONF` script variable, which defaults to ``meta-poky/conf/templates/default``
when you are building from the Yocto Project development environment,
-and to ``meta/conf/`` when you are building from the OpenEmbedded-Core
+and to ``meta/conf/templates/default`` when you are building from the OpenEmbedded-Core
environment. Because the script variable points to the source of the
``local.conf.sample`` file, this implies that you can configure your
build environment from any layer by setting the variable in the
top-level build environment setup script as follows::
- TEMPLATECONF=your_layer/conf
+ TEMPLATECONF=your_layer/conf/templates/your_template_name
Once the build process gets the sample
file, it uses ``sed`` to substitute final
@@ -281,7 +296,7 @@ file, it uses ``sed`` to substitute final
You can see how the :term:`TEMPLATECONF` variable is used by looking at the
``scripts/oe-setup-builddir`` script in the :term:`Source Directory`.
You can find the Yocto Project version of the ``local.conf.sample`` file in
- the ``meta-poky/conf`` directory.
+ the ``meta-poky/conf/templates/default`` directory.
.. _structure-build-conf-bblayers.conf:
@@ -301,14 +316,14 @@ you ``source`` the top-level build environment setup script (i.e.
As with the ``local.conf`` file, the source ``bblayers.conf.sample``
file used depends on the :term:`TEMPLATECONF` script variable, which
-defaults to ``meta-poky/conf/`` when you are building from the Yocto
-Project development environment, and to ``meta/conf/`` when you are
+defaults to ``meta-poky/conf/templates/default`` when you are building from the Yocto
+Project development environment, and to ``meta/conf/templates/default`` when you are
building from the OpenEmbedded-Core environment. Because the script
variable points to the source of the ``bblayers.conf.sample`` file, this
implies that you can base your build from any layer by setting the
variable in the top-level build environment setup script as follows::
- TEMPLATECONF=your_layer/conf
+ TEMPLATECONF=your_layer/conf/templates/your_template_name
Once the build process gets the sample file, it uses ``sed`` to substitute final
``${``\ :term:`OEROOT`\ ``}`` values for all ``##OEROOT##`` values.
@@ -317,17 +332,9 @@ Once the build process gets the sample file, it uses ``sed`` to substitute final
You can see how the :term:`TEMPLATECONF` variable is defined by the ``scripts/oe-setup-builddir``
script in the :term:`Source Directory`. You can find the Yocto Project
- version of the ``bblayers.conf.sample`` file in the ``meta-poky/conf/``
+ version of the ``bblayers.conf.sample`` file in the ``meta-poky/conf/templates/default``
directory.
-.. _structure-build-conf-sanity_info:
-
-``build/cache/sanity_info``
----------------------------
-
-This file indicates the state of the sanity checks and is created during
-the build.
-
.. _structure-build-downloads:
``build/downloads/``
@@ -366,14 +373,14 @@ remove the ``build/sstate-cache`` directory.
.. _structure-build-tmp-buildstats:
``build/tmp/buildstats/``
--------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~
This directory stores the build statistics.
.. _structure-build-tmp-cache:
``build/tmp/cache/``
---------------------
+~~~~~~~~~~~~~~~~~~~~
When BitBake parses the metadata (recipes and configuration files), it
caches the results in ``build/tmp/cache/`` to speed up future builds.
@@ -389,7 +396,7 @@ cache is reused. If the file has changed, it is reparsed.
.. _structure-build-tmp-deploy:
``build/tmp/deploy/``
----------------------
+~~~~~~~~~~~~~~~~~~~~~
This directory contains any "end result" output from the OpenEmbedded
build process. The :term:`DEPLOY_DIR` variable points
@@ -402,7 +409,7 @@ Project Overview and Concepts Manual.
.. _structure-build-tmp-deploy-deb:
``build/tmp/deploy/deb/``
--------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^
This directory receives any ``.deb`` packages produced by the build
process. The packages are sorted into feeds for different architecture
@@ -411,7 +418,7 @@ types.
.. _structure-build-tmp-deploy-rpm:
``build/tmp/deploy/rpm/``
--------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^
This directory receives any ``.rpm`` packages produced by the build
process. The packages are sorted into feeds for different architecture
@@ -420,14 +427,14 @@ types.
.. _structure-build-tmp-deploy-ipk:
``build/tmp/deploy/ipk/``
--------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^
This directory receives ``.ipk`` packages produced by the build process.
.. _structure-build-tmp-deploy-licenses:
``build/tmp/deploy/licenses/``
-------------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This directory receives package licensing information. For example, the
directory contains sub-directories for ``bash``, ``busybox``, and
@@ -440,7 +447,7 @@ section in the Yocto Project Development Tasks Manual.
.. _structure-build-tmp-deploy-images:
``build/tmp/deploy/images/``
-----------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This directory is populated with the basic output objects of the build
(think of them as the "generated artifacts" of the build process),
@@ -467,7 +474,7 @@ the kernel files::
.. _structure-build-tmp-deploy-sdk:
``build/tmp/deploy/sdk/``
--------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^
The OpenEmbedded build system creates this directory to hold toolchain
installer scripts which, when executed, install the sysroot that matches
@@ -479,7 +486,7 @@ Software Development Kit (eSDK) manual.
.. _structure-build-tmp-sstate-control:
``build/tmp/sstate-control/``
------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The OpenEmbedded build system uses this directory for the shared state
manifest files. The shared state code uses these files to record the
@@ -492,7 +499,7 @@ another.
.. _structure-build-tmp-sysroots-components:
``build/tmp/sysroots-components/``
-----------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This directory is the location of the sysroot contents that the task
:ref:`ref-tasks-prepare_recipe_sysroot`
@@ -507,7 +514,7 @@ should be automatic, and recipes should not directly reference
.. _structure-build-tmp-sysroots:
``build/tmp/sysroots/``
------------------------
+~~~~~~~~~~~~~~~~~~~~~~~
Previous versions of the OpenEmbedded build system used to create a
global shared sysroot per machine along with a native sysroot. Since
@@ -525,7 +532,7 @@ recipe-specific :term:`WORKDIR` directories. Thus, the
.. _structure-build-tmp-stamps:
``build/tmp/stamps/``
----------------------
+~~~~~~~~~~~~~~~~~~~~~
This directory holds information that BitBake uses for accounting
purposes to track what tasks have run and when they have run. The
@@ -545,7 +552,7 @@ section in the Yocto Project Overview and Concepts Manual.
.. _structure-build-tmp-log:
``build/tmp/log/``
-------------------
+~~~~~~~~~~~~~~~~~~
This directory contains general logs that are not otherwise placed using
the package's :term:`WORKDIR`. Examples of logs are the output from the
@@ -555,7 +562,7 @@ necessarily mean this directory is created.
.. _structure-build-tmp-work:
``build/tmp/work/``
--------------------
+~~~~~~~~~~~~~~~~~~~
This directory contains architecture-specific work sub-directories for
packages built by BitBake. All tasks execute from the appropriate work
@@ -587,7 +594,7 @@ install" places its output that is then split into sub-packages within
.. _structure-build-tmp-work-tunearch-recipename-version:
``build/tmp/work/tunearch/recipename/version/``
------------------------------------------------
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The recipe work directory --- ``${WORKDIR}``.
@@ -645,7 +652,7 @@ Here are key subdirectories within each recipe work directory:
.. _structure-build-work-shared:
``build/tmp/work-shared/``
---------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~
For efficiency, the OpenEmbedded build system creates and uses this
directory to hold recipes that share a work directory with other
@@ -695,7 +702,7 @@ distribution configuration file.
.. _structure-meta-conf-machine:
``meta/conf/machine/``
-----------------------
+~~~~~~~~~~~~~~~~~~~~~~
This directory contains all the machine configuration files. If you set
``MACHINE = "qemux86"``, the OpenEmbedded build system looks for a
@@ -706,7 +713,7 @@ support for a new machine to the Yocto Project, look in this directory.
.. _structure-meta-conf-distro:
``meta/conf/distro/``
----------------------
+~~~~~~~~~~~~~~~~~~~~~
The contents of this directory controls any distribution-specific
configurations. For the Yocto Project, the ``defaultsetup.conf`` is the
@@ -718,7 +725,7 @@ file mainly inherits its configuration from Poky.
.. _structure-meta-conf-machine-sdk:
``meta/conf/machine-sdk/``
---------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~
The OpenEmbedded build system searches this directory for configuration
files that correspond to the value of
diff --git a/poky/documentation/ref-manual/variables.rst b/poky/documentation/ref-manual/variables.rst
index cf817e9540..2971654531 100644
--- a/poky/documentation/ref-manual/variables.rst
+++ b/poky/documentation/ref-manual/variables.rst
@@ -135,7 +135,6 @@ system and gives an overview of their function and contents.
appear in :term:`DISTRO_FEATURES` within the current configuration, then
the recipe will be skipped, and if the build system attempts to build
the recipe then an error will be triggered.
-
:term:`APPEND`
An override list of append strings for each target specified with
@@ -729,22 +728,6 @@ system and gives an overview of their function and contents.
":ref:`dev-manual/common-tasks:building images for multiple targets using multiple configurations`"
section in the Yocto Project Development Tasks Manual.
- :term:`BBPATH`
- Used by BitBake to locate ``.bbclass`` and configuration files. This
- variable is analogous to the ``PATH`` variable.
-
- .. note::
-
- If you run BitBake from a directory outside of the
- :term:`Build Directory`, you must be sure to set :term:`BBPATH`
- to point to the Build Directory. Set the variable as you would any
- environment variable and then run BitBake::
-
- $ BBPATH = "build_directory"
- $ export BBPATH
- $ bitbake target
-
-
:term:`BBSERVER`
If defined in the BitBake environment, :term:`BBSERVER` points to the
BitBake remote server.
@@ -2386,8 +2369,8 @@ system and gives an overview of their function and contents.
.. note::
From a security perspective, hardcoding a default password is not
- generally a good idea or even legal in some jurisdictions. It is
- recommended that you do not do this if you are building a production
+ generally a good idea or even legal in some jurisdictions. It is
+ recommended that you do not do this if you are building a production
image.
Additionally there is a special ``passwd-expire`` command that will
@@ -2967,8 +2950,10 @@ system and gives an overview of their function and contents.
If you do not point to a script that you provide, the OpenEmbedded
build system uses the default script provided by the
- ``icecc-create-env.bb`` recipe, which is a modified version and not
- the one that comes with ``icecc``.
+ :oe_git:`icecc-create-env_0.1.bb
+ </openembedded-core/tree/meta/recipes-devtools/icecc-create-env/icecc-create-env_0.1.bb>`
+ recipe, which is a modified version and not the one that comes with
+ ``icecream``.
:term:`ICECC_PARALLEL_MAKE`
Extra options passed to the ``make`` command during the
@@ -3690,10 +3675,10 @@ system and gives an overview of their function and contents.
to "core-image-minimal-initramfs".
You can also find more information by referencing the
- ``meta-poky/conf/local.conf.sample.extended`` configuration file in
- the Source Directory, the :ref:`image <ref-classes-image>` class,
- and the :ref:`kernel <ref-classes-kernel>` class to see how to use
- the :term:`INITRAMFS_IMAGE` variable.
+ ``meta-poky/conf/templates/default/local.conf.sample.extended``
+ configuration file in the Source Directory, the :ref:`image
+ <ref-classes-image>` class, and the :ref:`kernel <ref-classes-kernel>`
+ class to see how to use the :term:`INITRAMFS_IMAGE` variable.
If :term:`INITRAMFS_IMAGE` is empty, which is the default, then no
initramfs image is built.
@@ -3752,7 +3737,7 @@ system and gives an overview of their function and contents.
configuration file. You cannot set the variable in a recipe file.
See the
- :yocto_git:`local.conf.sample.extended </poky/tree/meta-poky/conf/local.conf.sample.extended>`
+ :yocto_git:`local.conf.sample.extended </poky/tree/meta-poky/conf/templates/default/local.conf.sample.extended>`
file for additional information. Also, for information on creating an
initramfs, see the ":ref:`dev-manual/common-tasks:building an initial ram filesystem (initramfs) image`" section
in the Yocto Project Development Tasks Manual.
@@ -3984,11 +3969,10 @@ system and gives an overview of their function and contents.
KCONFIG_MODE = "alldefconfig"
-
:term:`KERNEL_ALT_IMAGETYPE`
Specifies an alternate kernel image type for creation in addition to
- the kernel image type specified using the
- :term:`KERNEL_IMAGETYPE` variable.
+ the kernel image type specified using the :term:`KERNEL_IMAGETYPE` and
+ :term:`KERNEL_IMAGETYPES` variables.
:term:`KERNEL_ARTIFACT_NAME`
Specifies the name of all of the build artifacts. You can change the
@@ -4172,9 +4156,12 @@ system and gives an overview of their function and contents.
when building the kernel and is passed to ``make`` as the target to
build.
- If you want to build an alternate kernel image type in addition to that
- specified by :term:`KERNEL_IMAGETYPE`, use the :term:`KERNEL_ALT_IMAGETYPE`
- variable.
+ To build additional kernel image types, use :term:`KERNEL_IMAGETYPES`.
+
+ :term:`KERNEL_IMAGETYPES`
+ Lists additional types of kernel images to build for a device in addition
+ to image type specified in :term:`KERNEL_IMAGETYPE`. Usually set by the
+ machine configuration files.
:term:`KERNEL_MODULE_AUTOLOAD`
Lists kernel modules that need to be auto-loaded during boot.
@@ -6075,9 +6062,9 @@ system and gives an overview of their function and contents.
:term:`PRSERV_HOST`
The network based :term:`PR` service host and port.
- The ``conf/local.conf.sample.extended`` configuration file in the
- :term:`Source Directory` shows how the
- :term:`PRSERV_HOST` variable is set::
+ The ``conf/templates/default/local.conf.sample.extended`` configuration
+ file in the :term:`Source Directory` shows how the :term:`PRSERV_HOST`
+ variable is set::
PRSERV_HOST = "localhost:0"
@@ -6588,7 +6575,7 @@ system and gives an overview of their function and contents.
:term:`SDK_CUSTOM_TEMPLATECONF`
When building the extensible SDK, if :term:`SDK_CUSTOM_TEMPLATECONF` is set to
- "1" and a ``conf/templateconf.conf`` file exists in the build directory
+ "1" and a ``conf/templateconf.cfg`` file exists in the build directory
(:term:`TOPDIR`) then this will be copied into the SDK.
:term:`SDK_DEPLOY`
@@ -7973,6 +7960,12 @@ system and gives an overview of their function and contents.
toolchain. You can use ``meta-sourcery`` as a template for adding
support for other external toolchains.
+ :term:`TC_CXX_RUNTIME`
+ Specifies the C/C++ STL and runtime variant to use during
+ the build process. Default value is 'gnu'
+
+ You can select "gnu", "llvm", or "android".
+
:term:`TEMPLATECONF`
Specifies the directory used by the build system to find templates
from which to build the ``bblayers.conf`` and ``local.conf`` files.
@@ -8666,7 +8659,8 @@ system and gives an overview of their function and contents.
USER_CLASSES ?= "buildstats"
For more information, see
- ``meta-poky/conf/local.conf.sample`` in the :term:`Source Directory`.
+ ``meta-poky/conf/templates/default/local.conf.sample`` in the
+ :term:`Source Directory`.
:term:`USERADD_ERROR_DYNAMIC`
If set to ``error``, forces the OpenEmbedded build system to produce
@@ -8924,4 +8918,3 @@ system and gives an overview of their function and contents.
On systems where many tasks run in parallel, setting a limit to this
can be helpful in controlling system resource usage.
-
generated by cgit v1.2.3 (git 2.39.0) at 2024-07-15 13:51:29 +0300