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

From KoanSoftware Wiki
Jump to: navigation, search
(BitBake requires Python 2.7.3 or later)
 
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
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-2012 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://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start]
−
 
 
−
    $ sudo dpkg-reconfigure dash               
 
  
 
The packages you need for a supported Ubuntu distribution are shown in the following command:
 
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 \
+
     $ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
−
    unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk \
+
     build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
−
     python-pysqlite2 diffstat help2man make gcc build-essential \
+
     xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \
−
     g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev \
+
     pylint3 xterm
−
     mercurial autoconf automake groff libtool xterm
 
  
 +
== Development Code - branch 3.1 'dunfell' LTS ==
  
−
The following list shows the required packages by function given a supported Ubuntu Linux distribution:
+
Yocto Project code can be found in the Yocto Project Source Repositories.
 +
To check out current development code using git:
  
−
* Essentials: Packages needed to build an image on a headless system:
+
$ cd $HOME/yocto
 +
$ git clone git://git.yoctoproject.org/poky -b dunfell
  
−
  $ sudo apt-get install gawk wget git-core diffstat unzip texinfo \
 
−
    build-essential chrpath
 
−
                           
 
  
−
* Graphical Extras: Packages recommended if the host system has graphics support:
+
$ cd $HOME/yocto/poky
 +
$ git clone git://git.openembedded.org/meta-openembedded -b dunfell
  
−
  $ sudo apt-get install libsdl1.2-dev xterm
+
poky/
−
                           
+
├── bitbake
 +
├── 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
  
−
* Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals:
+
== Initializing the Build Environment ==
  
−
  $ sudo apt-get install make xsltproc docbook-utils fop
+
From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:
−
                           
 
  
−
* ADT Installer Extras: Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer:
+
$ cd $HOME/yocto/poky
 +
$ source oe-init-build-env
  
−
  $ sudo apt-get install autoconf automake libtool libglib2.0-dev
+
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
  
−
== BitBake requires Python 2.7.3 or later ==
+
== Edit the configuration files ==
  
−
BitBake requires Python 2.7.3 or later so we install Python 2.7.5 manually in our Ubuntu 12.04 LTS
+
Edit $HOME/yocto/poky/build/conf/bblayers.conf
  
−
sudo apt-get install libreadline5-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev
+
 
−
+
  # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
−
  wget http://www.python.org/ftp/python/2.7.5/Python-2.7.5.tar.bz2
+
  # changes incompatibly
−
  tar xjvf Python-2.7.5.tar.bz2
+
  POKY_BBLAYERS_CONF_VERSION = "2"
−
  cd Python-2.7.5
 
 
   
 
   
−
  ./configure
+
  BBPATH = "${TOPDIR}"
−
  make
+
  BBFILES ?= ""
−
sudo make install
 
 
   
 
   
−
  python -V
+
  BBLAYERS ?= " \
 +
  /home/koan/yocto/poky/meta \
 +
  /home/koan/yocto/poky/meta-poky \
 +
  /home/koan/yocto/poky/meta-yocto-bsp \
 +
  /home/koan/yocto/poky/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"
  
−
== Development Code ==
+
== Building the Image ==
  
−
Yocto Project code can be found in the Yocto Project Source Repositories.
+
At this point, you need to select an image to build.
−
To check out current development code using git:
+
If this is your first build using the Yocto Project, you should try the smallest and simplest image:
  
−
    $ git clone git://git.yoctoproject.org/poky.git
+
$ bitbake core-image-minimal 
  
−
This creates a standard Poky tree
+
Now you just wait for the build to finish.
  
−
.
+
== Starting the QEMU Emulator ==
−
└── poky
 
−
    ├── bitbake
 
−
    ├── documentation
 
−
    ├── LICENSE
 
−
    ├── meta
 
−
    ├── meta-hob
 
−
    ├── meta-skeleton
 
−
    ├── meta-yocto
 
−
    ├── meta-yocto-bsp
 
−
    ├── oe-init-build-env
 
−
    ├── README
 
−
    ├── README.hardware
 
−
    └── scripts
 
  
−
== Initializing the Build Environment ==
+
Before you start the QEMU emulator, be sure you have already to set up the emulation environment.
−
 
 
−
From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:
 
  
−
    $ source poky/oe-init-build-env mybuilds
+
The following command setup the emulation environment and launch QEMU.
  
−
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, which is inside the Source Directory.
+
$ runqemu qemuarm
  
 +
Or if you prefer, open a new shell terminal, setup the environment again and run
  
−
== Building the Image ==
+
$ runqemu qemuarm nographic
−
 
 
−
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.
 
−
 
 
−
 
 
−
== Starting the QEMU Emulator ==
 
−
 
 
−
Before you start the QEMU emulator, be sure you have already to set up the emulation environment.
 
  
−
The following commands setup the emulation environment and launch QEMU. This example assumes the root filesystem (.ext3 file) and the pre-built kernel image file both reside in your home directory. The kernel and filesystem are for a 32-bit target architecture.
+
== Building cross-compiler ==
  
−
    $ runqemu qemux86 tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-minimal-qemux86.ext3
+
If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.
  
−
The environment in which QEMU launches varies depending on the filesystem image and on the target architecture. For example, if you source the environment for the ARM target architecture and then boot the minimal QEMU image, the emulator comes up in a new shell in command-line mode. However, if you boot the SDK image, QEMU comes up with a GUI.
+
$ bitbake meta-toolchain

Latest revision as of 15:15, 29 October 2020

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 Quick Start

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

    $ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
    build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
    xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \
    pylint3 xterm

Development Code - branch 3.1 'dunfell' 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 dunfell



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

poky/
├── bitbake
├── 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

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

Edit $HOME/yocto/poky/build/conf/bblayers.conf 


# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
 /home/koan/yocto/poky/meta \
 /home/koan/yocto/poky/meta-poky \
 /home/koan/yocto/poky/meta-yocto-bsp \
 /home/koan/yocto/poky/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=265"