http://192.168.180.206:8001/ 2026-05-13T00:27:06+00:00 http://192.168.180.206:8001/ http://192.168.180.206:8001/_media/wiki:dokuwiki.svg text/html 2025-04-02T15:16:05+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:autoversion?rev=1743606965&do=diff auto versioning If recipe points to not fixed version from git: SRC_URI = "git://example.com/project.git;protocol=ssh;branch=${SRCBRANCH}" SRCBRANCH = "devel" SRCREV = "devel" then version needs to be update for every change of source code. To detect change automatically and prevent sstate errors: text/html 2025-06-11T10:22:59+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:ci?rev=1749637379&do=diff CI Problems to solve: layers revision Change version of meta layers * repo: create another manifest with branch names, not hashes * kas: * use 2 sets of config (1st: pinned.yml 2nd: integration.yml) * use lockfiles single recipe revision text/html 2025-07-01T19:22:38+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:multiconfig?rev=1751397758&do=diff multiconfig 13 Building Images for Multiple Targets With Multiconfig With default - no multiconfig - usage bitbake works with one config local.conf. It is possible to use bitbake parallel tasks to build more targets and machines at the same time. When bitbake target is prefixed with special mc:configname:target text/html 2025-11-03T12:24:43+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:operators?rev=1762172683&do=diff Operators * = late evaluation (expand variable when used) * := immediately expand * += append (with space) * =+ prepend (with space) * .= append (without space) * =. prepend (without space) * ?= assign if no other value was assigned * text/html 2022-10-25T17:27:43+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:python?rev=1666718863&do=diff python packages pypi PYPI_PACKAGE = "CherryPy" SRC_URI[md5sum] = "867eadfc18a0a52bccf0a2958b84a538" SRC_URI[sha256sum] = "f1acd6d671cbc7d61edcb93a8e2aa11f55276b1460ef9ce1978dc21a5f852203" inherit pypi distutils/setuptools By default every recent Python package can be built: text/html 2026-03-10T18:27:24+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:split_packages?rev=1773167244&do=diff split packages How to customise /etc/fstab per image ? /etc/fstab is provided by base-files. * create base-files-X and base-files-Y packages with the same content as base-files with only changed /etc/fstab: <https:// yocto.yoctoproject.narkive.com/XcannnRd/per-image-customizations> * Search in Yocto for python populate_packages text/html 2025-04-13T16:00:17+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:tasks?rev=1744560017&do=diff tasks Bitbake tasks * fetch If needed, make local copy of remote sources (bz2, git, svn, ...). * unpack prepare source of package in work directory (bz2 - unpack, git - clone from local copy, etc) * patch apply all *.patch files from SRC_URI text/html 2025-11-18T09:16:13+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:tips?rev=1763457373&do=diff Tips * Overwriting Yocto Classes through meta-layer manual patching According to src/poky/meta/classes-recipe/kernel-yocto.bbclass kernel patches are skipped if 'patchdir' exists. ``kernel-yocto.bbclass`` cannot handle this special case so patches needs to be applied manually. OVERLAY_PREFIX="${SOURCE_PREFIX}/linux_5_15/overlay" SRC_URI:append = " \ file://0003-xxx.patch;patchdir=${OVERLAY_PREFIX};subdir=${OVERLAY_PREFIX} \ file://0004-xxx.patch;patchdir=${OVERLAY_PREFIX};… text/html 2026-03-05T18:45:26+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/sw:yocto:bitbake:vars?rev=1772736326&do=diff Variables * DEPENDS Lists a recipe's build-time dependencies. These are dependencies on other recipes whose contents (e.g. headers and shared libraries) are needed by the recipe at build time. * RDEPENDS Lists runtime dependencies of a package. These dependencies are other packages that must be installed in order for the package to function correctly.