LM
/
coreos
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

refactor: oe-init-build-env renamed to coreos-init-build-env

This commit is contained in:
Samuel Dolt 2022-10-04 15:18:41 +02:00
parent fb4838e2b6
commit c6a32c397c
2 changed files with 15 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
oe-init-build-env → coreos-init-build-env
View File

@ -1,7 +1,7 @@
#!/bin/sh
# This script is used to setup the OE Build Envrionment
# Normally this is called as '. ./oe-init-build-env <builddir>'
# Normally this is called as '. ./core-init-build-env <builddir>'
# On some shell, we can get the path of this script when sources. Otherwise we
# use the current directory as a fallback
@ -42,3 +42,14 @@ fi
# Call the oe-init-build-env scripts of openembedded-core
. "${OEROOT}/oe-init-build-env" "${1:-$CORE_OS_ROOT/build}"
# Add the scripts directory of CoreOS to the path
# Make sure our paths are at the beginning of $PATH
for newpath in "${CORE_OS_ROOT}/scripts"; do
# Remove any existences of $newpath from $PATH
PATH=$(echo $PATH | sed -re "s#(^|:)$newpath(:|$)#\2#g;s#^:##")
# Add $newpath to $PATH
PATH="$newpath:$PATH"
done
unset newpath
export PATH

6
documentation/quick-build.rst
View File

@ -72,12 +72,12 @@ Building an image
Before building an image, we have to first configure the build.
To create a build folder with our default configuration, you can run the `oe-init-build-env`
script:
To create a build folder with our default configuration, you can run the
`coreos-init-build-env` script:
.. code-block:: sh
~/core-os$ source oe-init-build-env
~/core-os$ source coreos-init-build-env
.. note::