linux/poky.git/scripts/oe-buildenv-internal, branch uninative-3.0

scripts/oe-buildenv-internal: Add pointer to scripts/install-buildtools

2020-04-01T10:44:24+00:00

If the minimum python version isn't met, show a pointer to the new install-buildtools script. (From OE-Core rev: 38e3d5bd3d05ed00a2fc55e3729cb8a6d4e4132f) Signed-off-by: Richard Purdie

oe-buildenv-internal: python 3.5 as min version

2020-04-01T10:44:23+00:00

Python 3.4 is EOL: https://www.python.org/downloads/release/python-3410/ The last supported distro was probably CentOS-7, which has python36 available from epel-7 or scl (as rh-python36) [1] [1] https://www.softwarecollections.org/en/scls/rhscl/rh-python36/ (From OE-Core rev: 20cdec283a2ee39daa2ffaace11daa764ba40606) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

scripts/oe-buildenv-internal: Add BB_LOGCONFIG

2020-03-12T22:53:40+00:00

We should allow the logging configurations to be specificed from the environment, for example for autobuilder setups. (From OE-Core rev: 66c9234b71791d2aab87068496aebdbd4eb1f5e2) Signed-off-by: Richard Purdie

hosttools: no longer check for or provide host python 2 to builds

2019-12-09T10:21:51+00:00

(From OE-Core rev: 5f8f16b17f66966ae91aeabc23e97de5ecd17447) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/lib+scripts: Convert to SPDX license headers

2019-05-09T15:31:55+00:00

This adds SPDX license headers in place of the wide assortment of things currently in our script headers. We default to GPL-2.0-only except for the oeqa code where it was clearly submitted and marked as MIT on the most part or some scripts which had the "or later" GPL versioning. The patch also drops other obsolete bits of file headers where they were encoountered such as editor modelines, obsolete maintainer information or the phrase "All rights reserved" which is now obsolete and not required in copyright headers (in this case its actually confusing for licensing as all rights were not reserved). More work is needed for OE-Core but this takes care of the bulk of the scripts and meta/lib directories. The top level LICENSE files are tweaked to match the new structure and the SPDX naming. (From OE-Core rev: f8c9c511b5f1b7dbd45b77f345cb6c048ae6763e) Signed-off-by: Richard Purdie

oe-init-buildenv/base: Relax python version checks in favour of HOSTTOOLS manipulation

2018-11-07T23:08:55+00:00

Several distros are now shipping "python" as python v3 contra to the original python guidelines. This causes users confusion/pain in trying to use our tools. We can just force "python" to "python2" within HOSTTOOLS to avoid this issue and hide the complexity from the user. (From OE-Core rev: b06a6cde5c5503f456f260c773cf126085e18c8d) Signed-off-by: Richard Purdie

oe-init-env: search 'bitbake' outside of oe-core

2018-03-01T22:13:56+00:00

atm, 'oe-init-build-env' expects 'bitbake' to be within the OE core git repository. This complicates the project setup because you have to manage the 'bitbake' directory or symlink manually (or specify the bitbake location explicitly). Looking for 'bitbake' outside the main git repository will ease project management significantly. Now, you can put everything into git submodules, clone the project with | git clone --recursive ... and continue immediately with | ..../oe-init-build-env E.g. when you had previously | . | |-- build/ | `-- sources/ | `-- org.openembedded.core/ | `-- bitbake -> ../bitbake (where 'bitbake' must be created manually after cloning the project), you can have now | . | |-- build/ | `-- sources/ | |-- bitbake/ | `-- org.openembedded.core/ which is completely managed by 'git'. Patch adds $OEROOT/.. to the search path for 'bitbake' (From OE-Core rev: 5b3afc9cfe38a9fb435fbe5fcabc59b9a60f4657) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie

oe-buildenv-internal: Fix finding build directory

2017-11-05T13:40:33+00:00

The intent of the env setup scripts is to set BBPATH to point at the build directory. This means if the user changes directory, bitbake can still find the original build directory. The default bblayers.conf files reset BBPATH to the correct components so this is safe and restores the behaviour the script was intended to have. [YOCTO #12163] (From OE-Core rev: 82eeb934997c9eaa6443079dfb649a89872a222c) Signed-off-by: Richard Purdie

oe-init-build-env-memres: Drop it

2017-07-21T07:44:25+00:00

With the new server structure we no longer need this separate environment init script. Just set BB_SERVER_TIMEOUT to be greater than zero and bitbake will remain in memory and the UI will auto-reconnect to it. Also clean out the old shutdown code from oe-init-build-env which also doesn't make sense now. (From OE-Core rev: a17724d687f9c04dc21f2f369da2b492f7119ba0) Signed-off-by: Richard Purdie

oe-buildenv-internal: show usage output

2016-12-13T22:55:21+00:00

Show usage text if script is not sourced. Tested in bash, zsh and dash. [YOCTO #10751] (From OE-Core rev: ac7a905b18acb8bd9b2412b6682afbe1d7e18d7b) Signed-off-by: Ed Bartosh Signed-off-by: Ross Burton Signed-off-by: Richard Purdie