linux/poky.git/documentation/ref-manual, branch mickledore

ref-manual: variables: add example for SYSROOT_DIRS variable

2023-10-25T14:51:01+00:00

(From yocto-docs rev: 11906c1497afb5876d8f5a9c50b4b0160ef4c8ec) Signed-off-by: Talel BELHAJSALEM Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: variables: add TOOLCHAIN_OPTIONS variable

2023-10-25T14:51:01+00:00

(From yocto-docs rev: c69126b44157a13ad2c7e69be65a7f6730c22690) Signed-off-by: Talel BELHAJSALEM Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: variables: add RECIPE_SYSROOT and RECIPE_SYSROOT_NATIVE

2023-10-25T14:51:01+00:00

(From yocto-docs rev: acdef1c3728b88f46d94415567fec85438a51ba4) Signed-off-by: Talel BELHAJSALEM Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: variables: provide no-match example for COMPATIBLE_MACHINE

2023-10-25T14:51:01+00:00

COMPATIBLE_MACHINE is used to forbid the use of a recipe or its packages for a specific set of machines. In some cases, it may make more sense to have the logic inverted and have the recipe always forbidden except for hand-picked machines. Such could be the case for pieces of software that only support some architectures. In that scenario, it is sometimes a bit easier on the eye and for maintenance to use the OVERRIDES mechanism but for that, a default should be set. COMPATIBLE_MACHINE:aarch64 = "^(aarch64)$" COMPATIBLE_MACHINE:mips64 = "^(mips64)$" wouldn't do much because if COMPATIBLE_MACHINE isn't set, the recipe is assumed compatible and therefore, if no default is provided we enter that case. Hence, we need to add COMPATIBLE_MACHINE = "^$" as default so that it only matches the empty string, which isn't possible for MACHINEOVERRIDES. Cc: Quentin Schulz (From yocto-docs rev: 051f868d1da1cbcd5726eb4c1e3f25946ce690e3) Signed-off-by: Quentin Schulz Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: Fix PACKAGECONFIG term and add an example

2023-10-25T14:51:01+00:00

PACKAGECONFIG's first and second flag value will be added to PACKAGECONFIG_CONFARGS and then it will be added to the appropriate variable (EXTRA_OECMAKE, or ...) So we need to only mention PACKAGECONFIG_CONFARGS and it will lead to other variables. I added a custom example that can help understanding very well PACKAGECONFIG. (From yocto-docs rev: 1bf0ac5c208d2d9609649bae681f37e3b4281c63) Signed-off-by: Talel BELHAJSALEM Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: Warn about COMPATIBLE_MACHINE skipping native recipes

2023-10-25T14:51:01+00:00

(From yocto-docs rev: 33cf8166a543a3fd76bb0e6cab03589c6d45f48c) Signed-off-by: Arne Schwerdt Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: releases.svg: Scarthgap is now version 5.0

2023-10-13T14:31:05+00:00

According to https://wiki.yoctoproject.org/wiki/Releases (From yocto-docs rev: 1d80812f27e21956124a5adcc81ac638e753cf37) Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: point outdated link to the new location

2023-09-29T14:33:44+00:00

(From yocto-docs rev: 08e04026d57450ea9496cdf8bf50c2f1fb033af5) Signed-off-by: Roland Hieber Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman

manuals: add new contributor guide

2023-09-13T16:21:26+00:00

(From yocto-docs rev: 77f20d1594db42818aac9a7a92865def8fb7ec36) Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman

ref-manual: system-requirements: update supported distros

2023-09-13T16:21:26+00:00

- Update according to changes in SANITY_TESTED_DISTROS (meta-poky/conf/distro/poky.conf) - No longer declare as "Supported" the distributions versions which are End of Life for their vendors, as some of them (Ubuntu for example) ship updates to subscribers only, which the Yocto Project has no access to. - List distribution versions which were previously tested for the branch of the Yocto Project being considered. (From yocto-docs rev: fd5113b7e20844a44a2c9da37e1bc10034d46cfe) Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman