学习yocto project 最好的文档，yocto project 官网上的Guide 文档：

https://www.yoctoproject.org/documentation/archived?keys=&field_version_tid=All

The Yocto Project Quick Start

http://www.yoctoproject.org/docs/1.2/yocto-project-qs/yocto-project-qs.html

Ubuntu 需要安装的package:

The packages you need for a supported Ubuntu distribution are shown in the following command:

$ sudo apt-get install sed wget cvs subversion git-core coreutils \unzip texi2html texinfo libsdl1.2-dev docbook-utils fop gawk \python-pysqlite2 diffstat help2man make gcc build-essential xsltproc \g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev \mercurial autoconf automake groff libtool xterm libxml-parser-perl

Initializing the Build Environment

From the parent directory of the Yocto Project Files, initialize your environment and provide a meaningful Yocto Project Build Directory name:

$ source poky/oe-init-build-env mybuilds

At this point, the mybuilds directory has been created for you and it is now your current working directory. If you don't provide your own directory name it defaults to build.

执行 source poky/oe-init-build-env mybuilds 是为了加载bitbake dev shell 环境，第一次初始化好环境，建立了mybuilds 文件夹，之后关闭terminal，再打开terminal 就无法输入bitbake 命令了，这时就需要重新执行

source poky/oe-init-build-env mybuilds 来加载 bitbake dev shell 环境。
bitbake 命令的参数可以直接输入 bitbake --help
bitbake -c -f 参数的意义：-f, --force           force run of specified cmd, regardless of stamp status-c CMD, --cmd=CMD     Specify task to execute. Note that this only executesthe specified task for the providee and the packagesit depends on, i.e. 'compile' does not implicitly callstage for the dependencies (IOW: use only if you knowwhat you are doing). Depending on the base.bbclass alisttasks tasks is defined and will show availabletasks

Running Specific Tasks

Any given package consists of a set of tasks. The standard BitBake behavior in most cases is:fetch, unpack, patch, configure, compile,install, package, package_write, and build. The default task isbuild and any tasks on which it depends build first. Some tasks exist, such asdevshell, that are not part of the default build chain. If you wish to run a task that is not part of the default build chain, you can use the-c option in BitBake as follows:

$ bitbake matchbox-desktop -c devshell

If you wish to rerun a task, use the -f force option. For example, the following sequence forces recompilation after changing files in the working directory.

$ bitbake matchbox-desktop..[make some changes to the source code in the working directory]..$ bitbake matchbox-desktop -c compile -f$ bitbake matchbox-desktop

This sequence first builds matchbox-desktop and then recompiles it. The last command reruns all tasks (basically the packaging tasks) after the compile. BitBake recognizes that thecompile task was rerun and therefore understands that the other tasks also need to be run again.

You can view a list of tasks in a given package by running thelisttasks task as follows:

$ bitbake matchbox-desktop -c listtasks

The results are in the file ${WORKDIR}/temp/log.do_listtasks.

Building the Image

At this point, you need to select an image to build for the BeagleBoard xM. If this is your first build using the Yocto Project, you should try the smallest and simplest image:

$ bitbake core-image-minimal

Now you just wait for the build to finish.

Here are some variations on the build process that could be helpful:

Run QEMU emulator

The final command runs the image:

$ runqemu qemux86

Board Support Packages (BSP) - Developer's Guide

http://www.yoctoproject.org/docs/1.2/yocto-project-qs/yocto-project-qs.html

BSP Layers

The BSP consists of a file structure inside a base directory. Collectively, you can think of the base directory and the file structure as a BSP Layer. BSP Layers use the following naming convention:

     meta-<bsp_name>

"bsp_name" is a placeholder for the machine or platform name.

The layer's base directory (meta-<bsp_name>) is the root of the BSP Layer. This root is what you add to theBBLAYERS variable in the conf/bblayers.conf file found in theYocto Project Build Directory. Adding the root allows the Yocto Project build system to recognize the BSP definition and from it build an image. Here is an example:

     BBLAYERS = " \/usr/local/src/yocto/meta \/usr/local/src/yocto/meta-yocto \/usr/local/src/yocto/meta-<bsp_name> \"

Some BSPs require additional layers on top of the BSP's root layer in order to be functional. For these cases, you also need to add those layers to theBBLAYERS variable in order to build the BSP. You must also specify in the "Dependencies" section of the BSP'sREADME file any requirements for additional layers and, preferably, any build instructions that might be contained elsewhere in theREADME file.

Some layers function as a layer to hold other BSP layers. An example of this type of layers is themeta-intel layer. Themeta-intel layer contains over 10 individual BSP layers.

For more detailed information on layers, see the "Understanding and Creating Layers" section of the Yocto Project Development Manual. You can also see the detailed examples in the appendices of The Yocto Project Development Manual.

Layer Configuration File

You can find this file in the BSP Layer at:

     meta-<bsp_name>/conf/layer.conf

The conf/layer.conf file identifies the file structure as a Yocto Project layer, identifies the contents of the layer, and contains information about how Yocto Project should use it. Generally, a standard boilerplate file such as the following works. In the following example, you would replace "bsp" and "_bsp" with the actual name of the BSP (i.e.<bsp_name> from the example template).

     # We have a conf and classes directory, add to BBPATHBBPATH := "${BBPATH}:${LAYERDIR}"# We have a recipes directory, add to BBFILESBBFILES := "${BBFILES} ${LAYERDIR}/recipes/*/*.bb \ ${LAYERDIR}/recipes/*/*.bbappend"BBFILE_COLLECTIONS += "bsp"BBFILE_PATTERN_bsp := "^${LAYERDIR}/"BBFILE_PRIORITY_bsp = "6"

To illustrate the string substitutions, here are the last three statements from the Crown Bayconf/layer.conf file:

     BBFILE_COLLECTIONS += "crownbay"BBFILE_PATTERN_crownbay := "^${LAYERDIR}/"BBFILE_PRIORITY_crownbay = "6"

This file simply makes BitBake aware of the recipes and configuration directories. The file must exist so that the Yocto Project build system can recognize the BSP.

     meta-<bsp_name>/conf/machine/*.conf

     include conf/machine/include/tune-atom.incinclude conf/machine/include/ia32-base.inc

Linux Kernel Configuration

You can find these files in the BSP Layer at:

     meta-<bsp_name>/recipes-kernel/linux/linux-yocto_*.bbappend

These files append your specific changes to the kernel you are using.

For your BSP, you typically want to use an existing Yocto Project kernel found in theYocto Project Files atmeta/recipes-kernel/linux. You can append your specific changes to the kernel recipe by using a similarly named append file, which is located in the BSP Layer (e.g. themeta-<bsp_name>/recipes-kernel/linux directory).

Suppose the BSP uses the linux-yocto_3.0.bb kernel, which is the preferred kernel to use for developing a new BSP using the Yocto Project.In other words, you have selected the kernel in your<bsp_name>.conf file by adding the following statements:

     PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"PREFERRED_VERSION_linux-yocto = "3.0%"

You would use the linux-yocto_3.0.bbappend file to append specific BSP settings to the kernel, thus configuring the kernel for your particular BSP.

As an example, look at the existing Crown Bay BSP. The append file used is:

     meta-crownbay/recipes-kernel/linux/linux-yocto_3.0.bbappend

The following listing shows the file. Be aware that the actual commit ID strings in this example listing might be different than the actual strings in the file from themeta-intel Git source repository.

     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"COMPATIBLE_MACHINE_crownbay = "crownbay"KMACHINE_crownbay  = "yocto/standard/crownbay"KERNEL_FEATURES_append_crownbay += " cfg/smp.scc"COMPATIBLE_MACHINE_crownbay-noemgd = "crownbay-noemgd"KMACHINE_crownbay-noemgd  = "yocto/standard/crownbay"KERNEL_FEATURES_append_crownbay-noemgd += " cfg/smp.scc"SRCREV_machine_pn-linux-yocto_crownbay ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"SRCREV_meta_pn-linux-yocto_crownbay ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"

This append file contains statements used to support the Crown Bay BSP for bothIntel® EMGD and the VESA graphics. The build process, in this case, recognizes and uses only the statements that apply to the defined machine name -crownbay in this case. So, the applicable statements in thelinux-yocto_3.0.bbappend file are follows:

     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"COMPATIBLE_MACHINE_crownbay = "crownbay"KMACHINE_crownbay  = "yocto/standard/crownbay"KERNEL_FEATURES_append_crownbay += " cfg/smp.scc"SRCREV_machine_pn-linux-yocto_crownbay ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"SRCREV_meta_pn-linux-yocto_crownbay ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"

The append file defines crownbay as the compatible machine and defines theKMACHINE. The file also points to some configuration fragments to use by setting theKERNEL_FEATURES variable. The location for the configuration fragments is the kernel tree itself in theYocto Project Build Directory underlinux/meta. Finally, the append file points to the specific commits in theYocto Project Files Git repository and themeta Git repository branches to identify the exact kernel needed to build the Crown Bay BSP.

One thing missing in this particular BSP, which you will typically need when developing a BSP, is the kernel configuration file (.config) for your BSP. When developing a BSP, you probably have a kernel configuration file or a set of kernel configuration files that, when taken together, define the kernel configuration for your BSP. You can accomplish this definition by putting the configurations in a file or a set of files inside a directory located at the same level as your append file and having the same name as the kernel. With all these conditions met simply reference those files in aSRC_URI statement in the append file.

For example, suppose you had a set of configuration options in a file called myconfig. If you put that file inside a directory named /linux-yocto and then added a SRC_URI statement such as the following to the append file, those configuration options will be picked up and applied when the kernel is built.

    SRC_URI += "file://myconfig"

As mentioned earlier, you can group related configurations into multiple files and name them all in theSRC_URI statement as well. For example, you could group separate configurations specifically for Ethernet and graphics into their own files and add those by using aSRC_URI statement like the following in your append file:

     SRC_URI += "file://myconfig \file://eth.cfg \file://gfx.cfg"

The FILESEXTRAPATHS variable is in boilerplate form in the previous example in order to make it easy to do that. This variable must be in your layer or BitBake will not find the patches or configurations even if you have them in your SRC_URI. The FILESEXTRAPATHS variable enables the build process to find those configuration files.

Customizing a Recipe for a BSP

If you plan on customizing a recipe for a particular BSP, you need to do the following:

To better understand this, consider an example that customizes a recipe by adding a BSP-specific configuration file namedinterfaces to thenetbase_4.47.bb recipe for machine "xyz". Do the following:

Using the Yocto Project's BSP Tools

The Yocto Project includes a couple of tools that enable you to create a BSP layer from scratch and do basic configuration and maintenance of the kernel without ever looking at a Yocto Project metadata file. These tools areyocto-bsp andyocto-kernel, respectively.

The following sections describe the common location and help features as well as details for theyocto-bsp andyocto-kernel tools.

     $ source oe-init-build-env [build_dir]

     $ yocto-bsp$ yocto-bsp helpUsage:Create a customized Yocto BSP layer.usage: yocto-bsp [--version] [--help] COMMAND [ARGS]The most commonly used 'yocto-bsp' commands are:create            Create a new Yocto BSPlist              List available values for options and BSP propertiesSee 'yocto-bsp help COMMAND' for more information on a specific command.Options:--version    show program's version number and exit-h, --help   show this help message and exit-D, --debug  output debug information

     $ yocto-bsp createUsage:Create a new Yocto BSPusage: yocto-bsp create <bsp-name> <karch> [-o <DIRNAME> | --outdir <DIRNAME>][-i <JSON PROPERTY FILE> | --infile <JSON PROPERTY_FILE>]This command creates a Yocto BSP based on the specified parameters.The new BSP will be a new Yocto BSP layer contained by default withinthe top-level directory specified as 'meta-bsp-name'.  The -o optioncan be used to place the BSP layer in a directory with a differentname and location....

     $ yocto-bsp help createNAMEyocto-bsp create - Create a new Yocto BSPSYNOPSISyocto-bsp create <bsp-name> <karch> [-o <DIRNAME> | --outdir <DIRNAME>][-i <JSON PROPERTY FILE> | --infile <JSON PROPERTY_FILE>]DESCRIPTIONThis command creates a Yocto BSP based on the specifiedparameters.  The new BSP will be a new Yocto BSP layer containedby default within the top-level directory specified as'meta-bsp-name'.  The -o option can be used to place the BSP layerin a directory with a different name and location.The value of the 'karch' parameter determines the set of filesthat will be generated for the BSP, along with the specific set of'properties' that will be used to fill out the BSP-specificportions of the BSP....NOTE: Once created, you should add your new layer to yourbblayers.conf file in order for it to be subsequently seen andmodified by the yocto-kernel tool.NOTE for x86- and x86_64-based BSPs: The generated BSP assumes thepresence of the of the meta-intel layer, so you should also have ameta-intel layer present and added to your bblayers.conf as well.

     $ yocto-bsp list karchArchitectures available:armpowerpci386mipsx86_64qemu

     $ yocto-bsp create myarm qemuWhich qemu architecture would you like to use? [default: x86]1) common 32-bit x862) common 64-bit x863) common 32-bit ARM4) common 32-bit PowerPC5) common 32-bit MIPS3Would you like to use the default (3.2) kernel? (Y/n)Do you need a new machine branch for this BSP (the alternative is to re-use an existing branch)? [Y/n]Getting branches from remote repo git://git.yoctoproject.org/linux-yocto-3.2...Please choose a machine branch to base this BSP on => [default: standard/default/common-pc]1) base2) standard/base3) standard/default/arm-versatile-926ejs4) standard/default/base5) standard/default/beagleboard6) standard/default/cedartrailbsp (copy).xml7) standard/default/common-pc-64/base8) standard/default/common-pc-64/jasperforest9) standard/default/common-pc-64/romley10) standard/default/common-pc-64/sugarbay11) standard/default/common-pc/atom-pc12) standard/default/common-pc/base13) standard/default/crownbay14) standard/default/emenlow15) standard/default/fishriver16) standard/default/fri217) standard/default/fsl-mpc8315e-rdb18) standard/default/mti-malta32-be19) standard/default/mti-malta32-le20) standard/default/preempt-rt21) standard/default/qemu-ppc3222) standard/default/routerstationpro23) standard/preempt-rt/base24) standard/preempt-rt/qemu-ppc3225) standard/preempt-rt/routerstationpro26) standard/tiny3Do you need SMP support? (Y/n)Does your BSP have a touchscreen? (y/N)Does your BSP have a keyboard? (Y/n)New qemu BSP created in meta-myarm

     BBLAYERS = " \/usr/local/src/yocto/meta \/usr/local/src/yocto/meta-yocto \/usr/local/src/yocto/meta-myarm \"

     $ yocto-kernelUsage:Modify and list Yocto BSP kernel config items and patches.usage: yocto-kernel [--version] [--help] COMMAND [ARGS]The most commonly used 'yocto-kernel' commands are:config list       List the modifiable set of bare kernel config options for a BSPconfig add        Add or modify bare kernel config options for a BSP config rm         Remove bare kernel config options from a BSPpatch list        List the patches associated with a BSPpatch add         Patch the Yocto kernel for a BSPpatch rm          Remove patches from a BSPSee 'yocto-kernel help COMMAND' for more information on a specific command.

     $ yocto-kernel patch add myarm ~/test.patchAdded patches:test.patch$ yocto-kernel patch add myarm ~/yocto-testmod.patchAdded patches:yocto-testmod.patch

     $ yocto-kernel patch list myarmThe current set of machine-specific patches for myarm is:1) test.patch2) yocto-testmod.patch

     $ yocto-kernel patch rm myarmSpecify the patches to remove:1) test.patch2) yocto-testmod.patch1Removed patches:test.patch

     $ yocto-kernel patch list myarmThe current set of machine-specific patches for myarm is:1) yocto-testmod.patch

     $ yocto-kernel config add myarm CONFIG_MISC_DEVICES=yAdded items:CONFIG_MISC_DEVICES=y$ yocto-kernel config add myarm KCONFIG_YOCTO_TESTMOD=yAdded items:CONFIG_YOCTO_TESTMOD=y

     $ yocto-kernel config list myarmThe current set of machine-specific kernel config items for myarm is:1) CONFIG_MISC_DEVICES=y2) CONFIG_YOCTO_TESTMOD=y

yocto project相关推荐

1. Yocto Project - basic - 01 - Quick Start

   Yocto 是一个被广泛使用的操作系统,本节开始介绍: 文章的内容来自于Yocto的官方介绍文档. 1 简介 The Yocto Project is an open-source collabora ...

2. [ 物联网篇 ] 02 - Yocto Project (YP)快速入门

   NXP i.MX 8M Mini 的源码构建系统使用的是Yocto,如果不熟悉Yocto,完全看不懂 i.MX 8M Mini 的相关代码. 废话不多说,直接到Yocto 官网看文档,写Demo.参考 ...

3. 《嵌入式Linux系统开发：基于 Yocto Project》笔记

   写在前面 这本书的"译者序"里面有这么一句话: 市面上不缺乏适用于各种开发语言的开发.编译和打包工具,但在Yocto项目出现前,这些零散的工作需要嵌入式开发者自己串起来以交付最终的 ...

4. YOCTO PROJECT安装

   1.按i.MX Yocto Project User's Guide.pdf里的第节开始,按文档一步步操作,UBNTU版本14.04.6 LTS(ubuntu-14.04.6-desktop-i386 ...

5. Freescale Yocto Project搭建

   系统:ubuntu-14.04.2 1.建立主机需要的包: A Freescale Yocto Project Community BSP build requires that some packa ...

6. 【i.MX8 Linux】构建 i.MX8 Yocto Project 映像

   本文所使用的构建主机是 i5 四核 8GB 内存的 Ubuntu 20.04,构建目标系统为 Linux 5.4 版本(Yocto 3.0 Zeus).官方建议在 Ubuntu 18.04 上操作,不 ...

7. 使用 Yocto Project 构建自定义嵌入式 Linux 发行版

   使用 Yocto Project 构建自定义嵌入式 Linux 发行版 转自: http://zzjlzx.blog.chinaunix.net/uid-9688646-id-5175371.html ...

8. Yocto Project 快速入门指南

   原文:http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project 快速入 ...

9. YOCTO项目介绍：通过提供模版、工具和方法帮助开发者创建基于linux内核的定制系统

   目录 YOCTO项目介绍 配置内核 build配套 Yocto ,是一个开源社区.它通过提供模版.工具和方法帮助开发者创建基于linux内核的定制系统,支持ARM, PPC, MIPS, x86 (3 ...

最新文章

1. php获取date前1分钟hour,php时间轴函数，刚、1分钟前、1小时前、一天前
2. linuxpython重定向_linux命令重定向、、 1、 2、 1、 2、
3. 综述：基于GAN的图像翻译模型盘点
4. java.lang.stackoverflowerror_java.lang.StackOverflowError——如何解决StackOverflowError错误
5. 大数据学习笔记46：初识日志收集系统Flume
6. jenkins手把手教你从入门到放弃03-安装Jenkins时web界面出现该jenkins实例似乎已离线
7. 最新易商支付源码/代付系统PHP源码+功能超级强大
8. 使用HTML实现图片切换/轮播
9. wordcloud python 如何不显示中文_Python词云库wordcloud中文显示问题详解
10. POJ 3295 Tautology （模拟法，栈的使用）
11. Android模拟器的判定
12. 有一个程序员男友是一种怎么样的体验？
13. mac如何在Finder中显示隐藏的文件或文件夹
14. 【大疆智图】| 重建三维模型
15. calibre-ebook 电子书阅读工具
16. 山西移动E900V21E_S905L3_线刷固件包
17. HTML超链接文字加粗,Markdown语法之--标题/注释/超链接/下划线/图片/代码/贯穿线/斜体加粗/列表，使你的文本更丰富...
18. 教学妹开发springboot+vue的博客论坛系统，so esay
19. Charles联动Burp-新世界的大门
20. Unity3D之SQLite的使用

热门文章

1. SpringBoot使用Freemarker导出word模板(OpenXML)
2. Unity开发VR——结合VRTK（一）
3. 【docker】docker容器搭建分布式LNMP，附错误及解决方案
4. 博思得打印机如何打印序列号标签
5. SpringBoot项目集成UniPush推送服务
6. 【Python编程入门】环境搭建
7. 【图像处理】常用色彩空间
8. Android MagicIndicator 指示器 导航
9. 数字图像处理 彩色图象处理
10. N32905音视频学习笔记-录音和播放