diff options
| -rwxr-xr-x | functions.sh | 1 | ||||
| -rwxr-xr-x | init-and-build.sh | 10 |
2 files changed, 11 insertions, 0 deletions
diff --git a/functions.sh b/functions.sh index b16467a..05d4b6a 100755 --- a/functions.sh +++ b/functions.sh @@ -305,6 +305,7 @@ OPTIONS: -r manifest repository -g GCC version (4.7 or 4.8) -u External Linaro toolchain URL + -i custom workspace init function -v Add -v[erbose] to bitbake invocation EOF } diff --git a/init-and-build.sh b/init-and-build.sh index 41c72e1..1c1b458 100755 --- a/init-and-build.sh +++ b/init-and-build.sh @@ -59,6 +59,16 @@ show_setup git_clone_update +# the purpose of the 'init' function is to prepare the <build> folder +# the default init function suitable for Linaro Platform builds, but +# the user can specify a custom function if needed. In any case, the +# init function must ensure : +# - oe-init-build-env is called +# - path is changed to <build> folder +# - user configuration files (local.conf, bblayers.conf, ..) are +# created. +# Once the build init is done, we are adding some Linaro CI specific +# build options, when running on Jenkins. if [ -z "$init_env" ]; then init_env else |