Difference between revisions of "Yocto Project my own quick start"

From KoanSoftware Wiki
Jump to: navigation, search
(→‎Edit the configuration files)
 
(55 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
This page is an excerpt from [http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2011 Linux Foundation]
+
This page is an excerpt from [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation]
  
  
−
== The Packages ==
+
== The required packages ==
  
−
Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu, Fedora, and openSUSE.
+
Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.
−
Ubuntu
 
  
−
If your distribution is Ubuntu, you need to be running the bash shell. You can be sure you are running this shell by entering the following command and selecting "No" at the prompt:
+
If you have different distributions, please refer to the [https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html Yocto Project Documentation]
  
−
    $ sudo dpkg-reconfigure dash               
+
You must install essential host packages on your build host.
 +
The following command installs the host packages based on an Ubuntu distribution:
  
−
The packages you need for a supported Ubuntu distribution are shown in the following command:
+
$ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \
 +
socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \
 +
python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1
 +
 +
$ sudo locale-gen en_US.UTF-8
  
−
    $ sudo apt-get install sed wget cvs subversion git-core coreutils \
+
== Development Code - branch 5.0 'scarthgap' LTS ==
−
    unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk \
 
−
    python-pysqlite2 diffstat help2man make gcc build-essential \
 
−
    g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev \
 
−
    mercurial autoconf automake groff libtool xterm
 
  
 +
Yocto Project code can be found in the Yocto Project Source Repositories.
 +
To check out current development code using git:
  
−
== Yocto versus Poky versus Angstrom ==
+
$ cd $HOME/yocto
 +
$ git clone git://git.yoctoproject.org/poky -b scarthgap
  
−
There’s a lot of talk about Yocto and Poky and Angstrom these days.  Unfortunately, there’s also a fair amount of confusion in the terms.  In some popular websites and presentations, the terms Yocto and Poky seem to be used interchangeably.  But there are quite unsubtle differences in the terms, and these differences will continue to grow over time, as other bits and pieces of technology find their way into Yocto.  And just what, exactly is Angstrom and how does it relate to Yocto? [http://blogs.mentor.com/chrishallinan/blog/2012/04/13/yocto-versus-poky-versus-angstrom-etc/ In this short article], Christopher Hallinan will attempt to provide some clarity around the various terms being thrown around in the Yocto space.
+
poky/
 +
├── bitbake
 +
├── contrib
 +
├── documentation
 +
├── LICENSE
 +
├── LICENSE.GPL-2.0-only
 +
├── LICENSE.MIT
 +
├── MAINTAINERS.md
 +
├── MEMORIAM
 +
├── meta
 +
├── meta-poky
 +
├── meta-selftest
 +
├── meta-skeleton
 +
├── meta-yocto-bsp
 +
├── oe-init-build-env
 +
├── README.hardware.md -> meta-yocto-bsp/README.hardware.md
 +
├── README.md -> README.poky.md
 +
├── README.OE-Core.md
 +
├── README.poky.md -> meta-poky/README.poky.md
 +
  ├── README.qemu.md
 +
├── scripts
 +
  └── SECURITY.md
 +
 
 +
In addition you can install an optional but frequently essential metalayer
 +
 
 +
$ cd $HOME/yocto/poky
 +
$ git clone git://git.openembedded.org/meta-openembedded -b scarthgap
 +
 
 +
== Initializing the Build Environment ==
 +
 
 +
From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:
 +
 
 +
$ cd $HOME/yocto/poky
 +
$ source oe-init-build-env
 +
 
 +
At this point, the '''build''' directory has been created for you and it is now your current working directory.
 +
This is the default tree you should have to build.
 +
 
 +
poky/
 +
├── bitbake
 +
├── build          <----- run bitbake inside here
 +
├── contrib
 +
├── documentation
 +
├── LICENSE
 +
├── LICENSE.GPL-2.0-only
 +
├── LICENSE.MIT
 +
├── meta
 +
├── meta-poky
 +
├── meta-selftest
 +
├── meta-skeleton
 +
├── meta-yocto-bsp
 +
├── oe-init-build-env
 +
  ├── README.hardware -> meta-yocto-bsp/README.hardware
 +
  ├── README.OE-Core
 +
  ├── README.poky -> meta-poky/README.poky
 +
├── README.qemu
 +
└── scripts
 +
 
 +
== Edit the configuration files ==
 +
 
 +
Add meta-openembedded/meta-oe to the bblayers.conf
 +
 
 +
bitbake-layers add-layer ../meta-openembedded/meta-oe
 +
 
 +
 
 +
Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf
 +
and check the following variables:
 +
 
 +
MACHINE ?= "qemuarm"
 +
DISTRO ?= "poky"
 +
PACKAGE_CLASSES ?= "package_ipk"
 +
INHERIT += "rm_work"
 +
 
 +
== Building the Image ==
 +
 
 +
At this point, you need to select an image to build.
 +
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.
 +
 
 +
== Starting the QEMU Emulator ==
 +
 
 +
Before you start the QEMU emulator, be sure you have already to set up the emulation environment.
 +
 
 +
The following command setup the emulation environment and launch QEMU.
 +
 
 +
$ runqemu qemuarm
 +
 
 +
Or if you prefer, open a new shell terminal, setup the environment again and run
 +
 
 +
$ runqemu qemuarm nographic
 +
 
 +
== Building cross-compiler ==
 +
 
 +
If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.
 +
 
 +
$ bitbake meta-toolchain

Latest revision as of 14:42, 17 October 2024

This page is an excerpt from Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation


The required packages

Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.

If you have different distributions, please refer to the Yocto Project Documentation

You must install essential host packages on your build host. The following command installs the host packages based on an Ubuntu distribution: 

$ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \
socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \
python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1

$ sudo locale-gen en_US.UTF-8

Development Code - branch 5.0 'scarthgap' LTS

Yocto Project code can be found in the Yocto Project Source Repositories. To check out current development code using git: 

$ cd $HOME/yocto
$ git clone git://git.yoctoproject.org/poky -b scarthgap

poky/
├── bitbake
├── contrib
├── documentation
├── LICENSE
├── LICENSE.GPL-2.0-only
├── LICENSE.MIT
├── MAINTAINERS.md
├── MEMORIAM
├── meta
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware.md -> meta-yocto-bsp/README.hardware.md
├── README.md -> README.poky.md
├── README.OE-Core.md
├── README.poky.md -> meta-poky/README.poky.md
├── README.qemu.md
├── scripts
└── SECURITY.md

In addition you can install an optional but frequently essential metalayer 

$ cd $HOME/yocto/poky
$ git clone git://git.openembedded.org/meta-openembedded -b scarthgap

Initializing the Build Environment

From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name: 

$ cd $HOME/yocto/poky
$ source oe-init-build-env

At this point, the build directory has been created for you and it is now your current working directory. This is the default tree you should have to build. 

poky/
├── bitbake
├── build          <----- run bitbake inside here
├── contrib
├── documentation
├── LICENSE
├── LICENSE.GPL-2.0-only
├── LICENSE.MIT
├── meta
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.OE-Core
├── README.poky -> meta-poky/README.poky
├── README.qemu
└── scripts

Edit the configuration files

Add meta-openembedded/meta-oe to the bblayers.conf 

bitbake-layers add-layer ../meta-openembedded/meta-oe


Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf and check the following variables: 

MACHINE ?= "qemuarm"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_ipk"
INHERIT += "rm_work"

Building the Image

At this point, you need to select an image to build. 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.

Starting the QEMU Emulator

Before you start the QEMU emulator, be sure you have already to set up the emulation environment.

The following command setup the emulation environment and launch QEMU. 

$ runqemu qemuarm

Or if you prefer, open a new shell terminal, setup the environment again and run 

$ runqemu qemuarm nographic

Building cross-compiler

If you want you can create a re-distribuible cross-compiler targeted at your MACHINE. 

$ bitbake meta-toolchain
Retrieved from "https://wiki.koansoftware.com/index.php?title=Yocto_Project_my_own_quick_start&oldid=376"