After updated init script, some new or changed options could be added or removed. After executed init script (step 2), the config sample file was renamed from ".sample" to "" and this file you can feed with your own options which have effect for all images you want to build.Īlternatively you can modify the default "$HOME/Build/poky-X.X//conf/nf" with your own requirements or include your own config file. This avoids possible conflicts during updating the init script from git repo. The origin cloned sample config file (".sample") should be untouched. The generated nf 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. bbappend 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. However, the Yoctoproject is veryĮxtensively documented and provides the best source of information. The possibilities for adjustments are very extensive and not really manageable for beginners. It does require a WebSVN instance to be set up so that you have a web based viewer for your repository. It's recommended to build for first time without any changes on config files to get an impression how the build process is working and see the results. We use FogBugz for bug tracking, it provides subversion commit scripts that allow you to include a case number in your check in comments and then associates the bug with the check in that fixed it. 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. Therefore, it is recommended to keep the sstate-cache directory. If you didn't delete the sstate-cache directory ($HOME/build/poky-X.X//sstate-cache), your image should be ready in a very fast time. That causes the complete reassembling of the image. If you want to force rebuild you can delete (or rename) the tmp directory ($HOME/build/poky-X.X//tmp):
If you want to reset your configs, please rename (delete is not recommended) the conf directory ($HOME/build/poky-X.X//conf) and execute the init script again. See also devtool and especially devtool modify.
#VISUALSVN 3.2 SCRIPTS FULL#
If You have moved any target source into the workspace tree you have full control to source code you want to modify. In this case you should transfer the desiered target source into the workspace repository ($HOME/builder/poky-X.X//workspace). Please check your configuration if required. New or modified config options are not considered. Note: Your config files will be untouched.
#VISUALSVN 3.2 SCRIPTS UPDATE#
The update routines will stash uncommitted changes or will rebase your local commits to new remote changes, but conflicts are possible. Of corse you can update and modiify your local meta-layer for meta-neutrino and machine layers repositories manually. See also " Working on target sources"! Update meta layer repositoriesĮxecution 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 If you moved some target sources into the workspace ($HOME/builder/poky-X.X//workspace), you must do it yourself. This will also update required dependencies. This will be done automatically on every called target with bitbake.
0 kommentar(er)
