linux/poky.git, branch genericarm64

local.conf.sample: add genericarm64

2024-02-21T10:19:00+00:00

Signed-off-by: Ross Burton

Add genericarm64 MACHINE

2024-02-21T10:17:45+00:00

This is a new 64-bit "generic" Arm machine, that expects the hardware to be SystemReady IR compatible. Signed-off-by: Ross Burton

core-image-initramfs-boot: always install all kernel modules

2024-02-21T10:17:45+00:00

The point of a "just boot" initramfs is to contain the kernel modules, so explicitly add all of the kernel modules to the image. Signed-off-by: Ross Burton

meson: use absolute cross-compiler paths

2024-02-20T12:58:41+00:00

Among the files generated by meson is compile_commands.json. It is not used by bitbake during the build. However, if the devtool workspace is opened inside an IDE, that IDE can use compile_commands.json to configure linting and code completion. This is notably relied on by the new devtool ide-sdk command. The problem is that the IDE using compile_commands.json does not know the $PATH set-up by bitbake, so it won't find the compiler. This results in linting errors, like missing headers. We can fix this by expliciting the absolute compiler paths in meson.cross. The compile_commands.json specification expressly states: "All paths specified in the command or file fields must be either absolute or relative to this directory." Link: https://clang.llvm.org/docs/JSONCompilationDatabase.html An alternative way to implement this is to directly change CXX inside bitbake.conf to make all recipes use absolute compiler paths.Since this would affect all recipes, so I would like to have the maintainers' opinion on this. It could make sense to use absolute compiler paths for all toolchain binaries, we already do so for the sysroot TOOLCHAIN_OPTIONS. Discussions have been opened with meson/ninja maintainers to implement this at their level: - https://github.com/ninja-build/ninja/issues/2383 - https://github.com/mesonbuild/meson/issues/12834 These tools have even less information on the environment so it makes sense for Yocto to provide the absolute paths. (From OE-Core rev: b4e00248049c2627b05eafa9313a48cf253623fa) Signed-off-by: Enguerrand de Ribaucourt Signed-off-by: Richard Purdie

devtool: ide: vscode: Configure read-only files

2024-02-20T12:58:41+00:00

When debugging or browsing files, the user may fall into external sources from other packages in the sysroot or dbg-rootfs. Modifying them will only lead to confusion since they will be overwritten by Yocto. The user should open them in a separate devtool modify session if they want to make changes. Meanwhile, we should prevent write access to them. (From OE-Core rev: 8a95ad9aecb81732c865e00a987bb8bd3d6cb91d) Signed-off-by: Enguerrand de Ribaucourt Signed-off-by: Richard Purdie

devtool: ide_sdk: Use bitbake's python3 for generated scripts

2024-02-20T12:58:41+00:00

The generated scripts use the sys.path configuration found inside bitbake. It can be a different python version than the one used on the host through the IDE. For instance, when running the generated script deploy_target_cmake-example-core2-64 from an eSDK generated on another machine, I got the following exception: AssertionError: SRE module mismatch We need to match the sys.executable to the sys.path. (From OE-Core rev: 45704319661570b45ef69fddd6b4b4fa22ca80d1) Signed-off-by: Enguerrand de Ribaucourt Signed-off-by: Richard Purdie

bitbake: Revert "bitbake: wget.py: always use the custom user agent"

2024-02-20T12:56:40+00:00

This reverts commit 987ab2a446aab235d6e86e97c05f25fb800d7acc. There's been a report that this breaks downloads from Jfrog Artifactory as self.user_agent is set to 'Mozilla Firefox', and when Artifactory sees that, it sends a response tailored for showing in an interactive browser (which in my opinion it has every right to). If we're using wget, we should say so via wget's default; handling uncooperative servers should be done on per-recipe basis, and ideally with tickets to admins of those servers. (Bitbake rev: feef5cd12e877f42ffcace168d44b0e6eb80a907) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bash: rebase the patch to fix ptest failure

2024-02-20T11:39:45+00:00

This fix commit oe-core: 1b69769b -- bash: changes to SIGINT handler while waiting for a child Due to the patch adjust and drop some codes to be applicable the tree, the line number has been changed, that cause test case "run-type" fail. (From OE-Core rev: ecb698ca5b4f76937dd3bee927465b17866d50be) Signed-off-by: Xiangyu Chen Signed-off-by: Richard Purdie

libsdl2: upgrade 2.28.5 -> 2.30.0

2024-02-20T11:39:45+00:00

License-Update: Copyright year updated to 2024. ChangeLog (https://github.com/libsdl-org/SDL/releases/tag/release-2.30.0): * Added support for 2 bits-per-pixel indexed surface formats * Added the function SDL_GameControllerGetSteamHandle() to get the Steam API handle for a controller, if available * Added the event SDL_CONTROLLERSTEAMHANDLEUPDATED which is sent when the Steam API handle for a controller changes. This could also change the name, VID, and PID of the controller. * Added the environment variable SDL_LOGGING to control default log output (From OE-Core rev: 7aef0ee68b612203fe5e0788c57642c4cabea1b4) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

insane.bbclass: Allow the warning about virtual/ to be disabled

2024-02-20T11:39:45+00:00

Commit f673d3d239799fb1ab50f4aa5d44187666aa0cd7 introduced a warning for virtual/ being used in RPROVIDES and RDEPENDS. Make it possible to disable the warning by removing "virtual-slash from WARN_QA. (From OE-Core rev: 968ffdb9fee5017eecce36ce878ea604c869ce95) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie