Update to the 5.1.2 release of the 5.1 series for buildtools.
(From OE-Core rev: 6766bce806a7e4fd62f6666db731eefc1b98c5ff)
Signed-off-by: Aleksandar Nikolic <aleksandar.nikolic@zeiss.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update to the 5.1.1 release of the 5.1 series for buildtools.
(From OE-Core rev: 0b746655fcc133db563d791673484c4ca82cda8a)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use the RawTextHelpFormatter formatter to preserve formatting in the
argpars help message.
(From OE-Core rev: ee94d7f99ff3c7e922fdb502fabbda3fd0cd8700)
Signed-off-by: Aleksandar Nikolic <aleksandar.nikolic@zeiss.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update to the 5.1 release of the 5.1 series for buildtools.
(From OE-Core rev: f6c1e5541ee8d215a0327263c9dd3f4cc128cd56)
Signed-off-by: Aleksandar Nikolic <aleksandar.nikolic@zeiss.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update to the 5.0.3 release of the 5.0 series for buildtools.
(From OE-Core rev: c922ca720a0c3b7b4d3d3187539e7cf77d93d457)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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-<arch>-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 <aleksandar.nikolic@zeiss.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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 <aleksandar.nikolic@zeiss.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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 <paul.eggleton@microsoft.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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 <richard.purdie@linuxfoundation.org>
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 <richard.purdie@linuxfoundation.org>
This fixes issues with openssl certs not working properly which meant error
reporting to an error report server was failing.
Also, all our downloads are now standarised on "sha256sum" so adjust for that.
(From OE-Core rev: bc8b44e19a05f499f5cef049eedbed1fede2e765)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The --check option turns on checksum validation, but it defaults to 'on'
so is pointless. Add a corresponding --no-check option to turn off
validation.
(From OE-Core rev: bf902a810f98f55dd9e8cb9e6c6b0903f9902157)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove all instances of the hardcoded 'x86_64' and replace with the current
host platform.
(From OE-Core rev: 52dc6f671ff67a1149be7ef4c65126ea3c907a3d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several failure paths were displaying an error message but not returning,
so the install process continued and failed further.
(From OE-Core rev: b00e28735b64a781707441ec6187dd7f9240d97a)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default, use the extended buildtools installer from the
Yocto Project 3.1 "dunfell" release.
(From OE-Core rev: abd9bf4428e024f4fbcabd75235965769c03f2db)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Our least common denominator supported distro is debian-8
which has python 3.4. The whole point of the install-buildtools
script is to make it easier on the user to install buildtools
tarball. So it needs to run on Python 3.4.
The way we checked if the install was successful in the prior
version of the script was not workable in python 3.4. Since
the environment-setup-... script is currently just exporting
environment variables, use os.environ to do the equivalent from
values gleaned via regex from the environment-setup-... file.
Corrected a couple minor whitespace errors
NOTE: License changed to GPL-2.0-only due to inclusion of code
copied directly from bitbake/lib/bb/utils.py. This avoids the
need to depend on bitbake, which is now Python 3.5+ only.
(From OE-Core rev: 869020dac889e9ed79a294f308a87cfd946a68bd)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add ability to check md5sum (yocto-3.1_M2 and before) or sha256
(yocto-3.1_M3 and beyond).
Make regex for path in checksum file optional, since
for yocto-3.1_M3 the format is <checksum> <filename>,
but prior releases was <checksum> <path><filename>
(From OE-Core rev: cb1c98f38755b8340140125064c21e407f39db74)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Install directory defaults to scripts/../buildtools
e.g. --directory is set by default
This avoids the user having to type in their sudo password
to install in /opt/poky/<installer-version>
* Use "." rather than "source" for sourcing the environment script
as not all distros (e.g. Debian) have "source" by default.
* Add buildtools/ to .gitignore
* Fix typos in example usage (--install-version -> --installer-version)
[YOCTO #13832]
(From OE-Core rev: c6c3a58dbf0ca6c4a41df7ff50fa56d39d7ee23f)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For distros such as CentOS-7 where the default buildtools are too
old we need to make it easy for users to install a pre-built SDK
with all of "build-essentials" included.
Other uses may include building older Yocto Project releases with
a distro where buildtools are too new.
For convenience, the standard buildtools installation is also
supported.
NOTE: extended buildtools is the default, e.g.
--with-extended-buildtools is on by default
Example usage (extended buildtools from milestone):
(1) using --url and --filename
$ install-buildtools \
--url http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.1_M2/buildtools \
--filename x86_64-buildtools-extended-nativesdk-standalone-3.0+snapshot-20200122.sh
(2) using --base-url, --release, --installer-version and --build-date
$ install-buildtools \
--base-url http://downloads.yoctoproject.org/releases/yocto \
--release yocto-3.1_M2 \
--install-version 3.0+snapshot
--build-date 202000122
Example usage (standard buildtools from release):
(3) using --url and --filename
$ install-buildtools --without-extended-buildtools \
--url http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.2/buildtools \
--filename x86_64-buildtools-nativesdk-standalone-3.0.2.sh
(4) using --base-url, --release and --installer-version
$ install-buildtools --without-extended-buildtools \
--base-url http://downloads.yoctoproject.org/releases/yocto \
--release yocto-3.0.2 \
--install-version 3.0.2
[YOCTO #13832]
(From OE-Core rev: 2d0aea6a73c427ce6aa17dc71e0783977a52bb2b)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
