linux/poky.git/scripts/install-buildtools, branch walnascar-next

scripts/install-buildtools: write download URLs to files for traceability

2025-03-17T17:09:22+00:00

This extends the previous commit, so that download URLs are preserved in addition to actual artefacts. By default it's all written to a temporary directory and erased together with artefacts, but users can choose to preserve both: $ install-buildtools -D --downloads-directory=. ... $ ls -1 buildtools_url checksum_url x86_64-buildtools-extended-nativesdk-standalone-5.1.2.sh x86_64-buildtools-extended-nativesdk-standalone-5.1.2.sh.sha256sum Additionally, rename check_url variable into checksum_url as it's a better name. (From OE-Core rev: 76748d27fd5088971259d08fdeae5c86a054452b) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

scripts/install-buildtools: add an option to specify where downloads go

2025-03-17T17:09:22+00:00

By default the script puts everything it downloads into a temporary directory and erases it after unpacking and installing the buildtools. This isn't great for traceability and reproducibility of builds (being able to see what was downloaded exactly, and being able to reproduce setting up a build, especially if the buildtools download location isn't available for whatever reason). This commit adds an option to download items into a specified directory and keep them there. I would particularly like to use it with bitbake-setup, where an optional feature to install the buildtools (exact implementation details tbd) would ensure the tarball remains available on local disk. (From OE-Core rev: fc8cedd899f7e5d06215a71808dd0827ccdcf849) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

scripts/install-buildtools: Update to 5.1.2

2025-02-18T22:53:44+00:00

Update to the 5.1.2 release of the 5.1 series for buildtools. (From OE-Core rev: 6766bce806a7e4fd62f6666db731eefc1b98c5ff) Signed-off-by: Aleksandar Nikolic Signed-off-by: Richard Purdie

scripts/install-buildtools: Update to 5.1.1

2024-12-13T12:26:01+00:00

Update to the 5.1.1 release of the 5.1 series for buildtools. (From OE-Core rev: 0b746655fcc133db563d791673484c4ca82cda8a) Signed-off-by: Antonin Godard Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

scripts/install-buildtools: preserve formatting in the help message

2024-12-09T15:23:28+00:00

Use the RawTextHelpFormatter formatter to preserve formatting in the argpars help message. (From OE-Core rev: ee94d7f99ff3c7e922fdb502fabbda3fd0cd8700) Signed-off-by: Aleksandar Nikolic Signed-off-by: Richard Purdie

scripts/install-buildtools: Update to 5.1

2024-11-23T14:44:54+00:00

Update to the 5.1 release of the 5.1 series for buildtools. (From OE-Core rev: f6c1e5541ee8d215a0327263c9dd3f4cc128cd56) Signed-off-by: Aleksandar Nikolic Signed-off-by: Richard Purdie

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