mirrors/buildenv
1
0
Fork 0
mirror of https://github.com/tuxbox-neutrino/buildenv.git synced 2025-08-26 23:13:18 +02:00
Code Issues Packages Projects Releases Wiki Activity

update README.md

Browse Source 
Revoved obsolete parameters and version 3.0, 3.1, only v3.2 supported
Only one parameter is reqiured now
This commit is contained in:
Thilo Graf
2022-06-12 15:00:50 +02:00
parent 635dcea62b
commit 53c1eff2d9
1 changed files with 20 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
README.md
View File

@@ -36,15 +36,14 @@ $:~ cd build
## 2. Execute init script ## 2. Execute init script
This will clone all required layers and create some config files into your build directories. This will clone all required layers and create some config files into your build directories.
* Parameter 1 <machine>: could be h7, hd51, hd60, hd61, osmio4k, osmio4kplus or set 'all' or keep empty ' ' for all machines. * Parameter <machine>: could be bre2ze4k, h7, hd51, hd60, hd61, osmio4k, osmio4kplus or set 'all' or keep empty ' ' for all machines.
* Parameter 2 <image-version>: could be 3.0, 3.1, 3.2 (default) or keep empty for default version (recommended, older versions are not really maintained anymore)
```bash ```bash
$:~ ./init.sh <machine> <image-version> $:~ ./init.sh <machine>
$:~ cd poky-<image-version> $:~ cd poky-3.2
``` ```
example: example:
```bash ```bash
$:~ ./init.sh hd51 3.2 $:~ ./init.sh hd51
$:~ cd poky-3.2 $:~ cd poky-3.2
``` ```
@@ -70,7 +69,7 @@ Other commonly useful commands are:
- 'devtool' and 'recipetool' handle common recipe tasks - 'devtool' and 'recipetool' handle common recipe tasks
- 'bitbake-layers' handles common layer tasks - 'bitbake-layers' handles common layer tasks
- 'oe-pkgdata-util' handles common target package tasks - 'oe-pkgdata-util' handles common target package tasks
tuxbox@tuxbox-builder:~/Build/poky-3.0/hd51 tuxbox@tuxbox-builder:~/Build/poky-3.2/hd51
$ $
``` ```
**NOTE:** If you left the current shell you must retry [step 3](#3-execute-environment-script) for your machine type to recreate the required environment. **NOTE:** If you left the current shell you must retry [step 3](#3-execute-environment-script) for your machine type to recreate the required environment.
@@ -92,7 +91,7 @@ NOTE: Tasks Summary: Attempted 4568 tasks of which 4198 didn't need to be rerun
Built images and packages to find under: Built images and packages to find under:
``` ```
~/build/poky-X.X/<machine>/tmp/deploy ~/build/poky-3.2/<machine>/tmp/deploy
``` ```
or in the dist directory: or in the dist directory:
``` ```
@@ -102,7 +101,7 @@ or in the dist directory:
## Updating ## Updating
### Update target sources ### Update target sources
An explicit update for any sources (e.g. neutrino) is not required. This will be done automatically on every called target with bitbake. This will also update required dependencies. If you moved some target sources into the workspace ($HOME/builder/poky-X.X/<machine>/workspace), you must do it yourself. See also "[Working on target sources](#working-on-target-sources)"! An explicit update for any sources (e.g. neutrino) is not required. This will be done automatically on every called target with bitbake. This will also update required dependencies. If you moved some target sources into the workspace ($HOME/builder/poky-3.2/<machine>/workspace), you must do it yourself. See also "[Working on target sources](#working-on-target-sources)"!
### Update meta layer repositories ### Update meta layer repositories
Execution of init script will update the yocto poky-x.x repository to the required yocto release and will updating the included local meta layers to current Execution of init script will update the yocto poky-x.x repository to the required yocto release and will updating the included local meta layers to current
@@ -111,18 +110,18 @@ state of remote repositories. Of corse you can update and modiify your local met
**Note: Your config files will be untouched. New or modified config options are not considered. Please check your configuration if required.** **Note: Your config files will be untouched. New or modified config options are not considered. Please check your configuration if required.**
## Working on target sources ## Working on target sources
In this case you should transfer the desiered target source into the workspace repository ($HOME/builder/poky-X.X/<machine>/workspace). In this case you should transfer the desiered target source into the workspace repository ($HOME/builder/poky-3.2/<machine>/workspace).
If You have moved any target source into the workspace tree you have full control to source code you want to modify. See also [devtool](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-devtool-in-your-sdk-workflow) and especially [devtool modify](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component). If You have moved any target source into the workspace tree you have full control to source code you want to modify. See also [devtool](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-devtool-in-your-sdk-workflow) and especially [devtool modify](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component).
## Reset configuration if required ## Reset configuration if required
If you want to reset your configs, please rename (delete is not recommended) the conf directory ($HOME/build/poky-X.X/<machine>/conf) and execute the init script again. If you want to reset your configs, please rename (delete is not recommended) the conf directory ($HOME/build/poky-3.2/<machine>/conf) and execute the init script again.
## Force complete rebuild ## Force complete rebuild
If you want to force rebuild you can delete (or rename) the tmp directory ($HOME/build/poky-X.X/<machine>/tmp): If you want to force rebuild you can delete (or rename) the tmp directory ($HOME/build/poky-3.2/<machine>/tmp):
``` ```
~/build/poky-X.X/<machine>/tmp ~/build/poky-3.2/<machine>/tmp
``` ```
That causes the complete reassembling of the image. If you didn't delete the sstate-cache directory ($HOME/build/poky-X.X/<machine>/sstate-cache), your image should be ready in a very fast time. Therefore, it is recommended to keep the sstate-cache directory. That causes the complete reassembling of the image. If you didn't delete the sstate-cache directory ($HOME/build/poky-3.2/<machine>/sstate-cache), your image should be ready in a very fast time. Therefore, it is recommended to keep the sstate-cache directory.
In rare cases it should be necessary to delete this directory as well. Please note, however, in this case the build will take much more time. In rare cases it should be necessary to delete this directory as well. Please note, however, in this case the build will take much more time.
## Customize if required ## Customize if required
@@ -133,12 +132,12 @@ extensively documented and provides the best source of information.
**Please do not modify the Yocto-sources! This is not recommended by the Yocto-Team, but you can use [.bbappend](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files) files to complete, expand or override meta core Yocto recipes.** **Please do not modify the Yocto-sources! This is not recommended by the Yocto-Team, but you can use [.bbappend](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files) files to complete, expand or override meta core Yocto recipes.**
The generated local.conf contains only a few lines but contains a line which is pointing to a common config file and is valid for all images and supported machine types to keep an unified image structure. The origin cloned sample config file ("local.conf.common.inc.sample") should be untouched. This avoids possible conflicts during updating the init script from git repo. After executed init script (step 2), the config sample file was renamed from "local.conf.common.inc.sample" to "local.conf.common.inc" and this file you can feed with your own options which have effect for all images you want to build. The generated local.conf contains only a few lines but contains a line which is pointing to a common config file and is valid for all images and supported machine types to keep an unified image structure. The origin cloned sample config file ("local.conf.common.inc.sample") should be untouched. This avoids possible conflicts during updating the init script from git repo. After executed init script (step 2), the config sample file was renamed from "local.conf.common.inc.sample" to "local.conf.common.inc" and this file you can feed with your own options which have effect for all images you want to build.
Alternatively you can modify the default "$HOME/Build/poky-X.X/<machine>/conf/local.conf" with your own requirements or include your own config file. After updated init script, some new or changed options could be added or removed. This case you should consider for your own configuration. Alternatively you can modify the default "$HOME/Build/poky-3.2/<machine>/conf/local.conf" with your own requirements or include your own config file. After updated init script, some new or changed options could be added or removed. This case you should consider for your own configuration.
### Overview of global configuration files ### Overview of global configuration files
For local configuration these config files within your build directory are required: For local configuration these config files within your build directory are required:
``` ```
$HOME/build/poky-X.X/<machine>/conf/bblayers.conf $HOME/build/poky-3.2/<machine>/conf/bblayers.conf
``` ```
Default generated configuration for bblayers.conf: Default generated configuration for bblayers.conf:
@@ -153,11 +152,11 @@ BBPATH = "${TOPDIR}"
BBFILES ?= "" BBFILES ?= ""
BBLAYERS ?= " \ BBLAYERS ?= " \
${HOME}/build/poky-X.X/meta \ ${HOME}/build/poky-3.2/meta \
${HOME}/build/poky-X.X/meta-poky \ ${HOME}/build/poky-3.2/meta-poky \
${HOME}/build/poky-X.X/meta-yocto-bsp \ ${HOME}/build/poky-3.2/meta-yocto-bsp \
${HOME}/build/poky-X.X/meta-neutrino \ ${HOME}/build/poky-3.2/meta-neutrino \
${HOME}/build/poky-X.X/poky/meta-<metaname> \ ${HOME}/build/poky-3.2/poky/meta-<metaname> \
" "
# the following entries are experimental and are required to build kodi and some qt related stuff e.g. qtwebengine ... # the following entries are experimental and are required to build kodi and some qt related stuff e.g. qtwebengine ...
@@ -171,7 +170,7 @@ BBLAYERS += " \
The general configuration you will find here, mostly entries are described inside these files: The general configuration you will find here, mostly entries are described inside these files:
``` ```
$HOME/build/poky-X.X/<machine>/conf/local.conf $HOME/build/poky-3.2/<machine>/conf/local.conf
$HOME/build/local.conf.common.inc $HOME/build/local.conf.common.inc
``` ```