linux/poky.git/scripts/install-buildtools, branch styhead-5.1.4

scripts/install-buildtools: Update to 5.1.2

2025-02-21T14:34:58+00:00

Update to the 5.1.2 release of the 5.1 series for buildtools. (From OE-Core rev: 1d6d438b10f5956d523742c5357e7942f8d154fd) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.1

2024-11-30T13:41:59+00:00

Update to the 5.1 release of the 5.1 series for buildtools. (From OE-Core rev: 4f58037a49ef538d89d9c6df81b1b2d8a2eab4d7) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 5.0.3

2024-09-17T11:25:21+00:00

Update to the 5.0.3 release of the 5.0 series for buildtools. (From OE-Core rev: c922ca720a0c3b7b4d3d3187539e7cf77d93d457) Signed-off-by: Richard Purdie

install-buildtools: update base-url, release and installer version

2024-06-12T15:08:32+00:00

Update the following default values: - DEFAULT_BASE_URL (https instead of http) - DEFAULT_RELEASE (5.0.1) - DEFAULT_INSTALLER_VERSION (5.0.1) (From OE-Core rev: b2ebb965a5aa128b05ed7ddc9216171463777732) Signed-off-by: Aleksandar Nikolic Signed-off-by: Richard Purdie

install-buildtools: fix "test installation" step

2024-06-12T15:08:32+00:00

The "Test installation" step fails with some harmless error messages (see [1]). This can however make a user think that the buildtools have not been installed correctly. Two reasons for the error messages: - some envvars in the environment-setup--pokysdk-linux file start and end with double quotes (e.g., PATH) and are as such written into python os.environ. This leads that their usage is not valid later when testing the installation. This patch removes the double quotes before writing, if they are present. - if installation directory (install_dir), given through the option --directory, is given as a relative path, checking if the path to a tool (e.g., gcc) in buildtools starts it will always fail. This patch converts the install_dir variable to an absolute path. [1] ERROR: Something went wrong: tar not found in ./build-tools ERROR: Something went wrong: installation failed (From OE-Core rev: e4eb0b14ecf9bd2fba13260441c9d86eb348f41e) Signed-off-by: Aleksandar Nikolic Signed-off-by: Richard Purdie

install-buildtools: remove md5 checksum validation

2024-06-12T15:08:32+00:00

No need to validate with the md5 checksum, as the file is not even uploaded to the Yocto release webpage (the download never failed due to a wrong indentation of an else statement). For validation purposes, use the sha256 checksum only. (From OE-Core rev: b740d2f9d40aef1e18c022d1e82b4fb2c5c1fc22) Signed-off-by: Aleksandar Nikolic Signed-off-by: Richard Purdie

install-buildtools: support buildtools-make-tarball and update to 4.1

2022-10-25T12:42:02+00:00

Support installing buildtools-make-tarball that is built in version 4.1 and later for build hosts with a broken make version. Also update the default version values to 4.1. (From OE-Core rev: 5d539268d0c7b8fad1ba9352c7f2d4b81e78b75c) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

buildtools-installer: Update to use 3.4

2022-01-12T21:09:01+00:00

This updates buildtools to use the tarball from the 3.4 release which contains some bug fixes and is what the autobuilder currently uses for testing on older distros. (From OE-Core rev: 7479861c60a1c205b9502c1a811ac3a9dc51cd07) Signed-off-by: Richard Purdie

scripts/install-buildtools: Update to 3.2 M3 buildtools

2020-10-20T10:11:45+00:00

(From OE-Core rev: 89a94ad07b641434089b0684bec0acd8fa8f97c1) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

scripts/install-buildtools: Handle new format checksum files

2020-06-25T09:23:37+00:00

Autobuilder generated checksum files only have a single space between the sum and the filename, tweak it to account for this. (From OE-Core rev: d1e71bf5b399372166eb40bb0d99c8fb52231600) Signed-off-by: Richard Purdie