Yocto Project™ 是一个开源的协作软件,提供模板、工具和方法帮你创建定制的 Linux 系统和嵌入+式产品,而无需关心硬件体系。适合嵌入式Linux开发人员使用。查看Yocto
Project Quick Start
相关术语
Poky
Poky是Yocto Project的参考发布版本。它包括OpenEmbedded构建系统(BitBake and OpenEmbedded Core)和一系列metadata,帮助开发者构建自己的distro。你可以下载Poky和使用它去逐步搭建自己的发布版本。需要注意的是Poky不包括二进制文件,它是一个关于搭建编译你自己制定的Linux发布版本的一个源代码用例。
Freescale provides an additional layer called the Freescale BSP Release, named meta-fsl-bsp-release, to integrate a new Freescale release with the FSL Yocto Project Community BSP.
Freescale i.MX boards are configured in the meta-fsl-bsp-release and meta-fsl-arm layers. This includes U-Boot, the Linux kernel, and reference board-specific details.
L4.1.15_2.0.0_ga is a Linux kernel that Freescale has released only for the Yocto Project.
Freescale L4.1.15_2.0.0_ga uses device trees. Device tree settings are found in the i.MX machine configuration files.
Graphics recipes integrate the Freescale graphics package release. For the i.MX boards that have a GPU, the imxgpu-viv recipes package the graphic components for each DISTRO – X11, frame buffer (FB), Xwayland,Wayland backend, and Weston compositor (Weston).
Freescales provideds a script, fsl-setup-release.sh, that simplifies the setup for i.MX machines. To use the script, the name of the specific machine to be built for needs to be specified as well as the graphical backend desired. The script sets up a directory
and the configuration files for the specified machine and backend.
The Yocto Project build uses the bitbake command. For example, bitbake builds the named component. Each component build has multiple tasks, such as fetching, configuration, compilation, packaging, and deploying to the target rootfs. The bitbake image build
gathers all the components required by the image and build in order of the dependency per task. The first build is the toolchain along with the tools required for the components to build.
If a new terminal window is opened or the machine is rebooted after a build directory is set up, the setup environment script should be used to set up the environment variables and run a build again. The full fsl-setup-release.sh is not needed.
$ source setup-environment
Aftera build is complete, the created image resides in /tmp/deploy/images. An image is, for the most part, specific to the machine set in the environment setup. Each image build creates a U-Boot, a kernel, and an image type based on the IMAGE_FSTYPES defined
in the machine configuration file. Most machine configurations provide an SD card image (.sdcard), an ext3 and tar.bz2. The ext3 is the root file system only. The .sdcard image contains U-Boot, the kernel and the rootfs completely set up for use on an SD card.