KoanSoftware Wiki - User contributions [en]

MediaWiki:Common.css

2025-11-01T14:58:44Z

Admin: bullet

/* CSS placed here will be applied to all skins */

* {
font-family: "Arial", "Helvetica", sans-serif !important;
}

a {
color: #911017;
}

a:visited {
color: #911017;
}

a.new,
#p-personal a.new {
color: #cc2200;
}

ul {
list-style-image: url('/skins/Koan25/bullet.gif');
}

Main Page

2025-11-01T14:56:48Z

Admin: more spaces

Welcome on [https://koansoftware.com Koan Software] official wiki

== KOAN Embedded Software Engineering ==
[https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.

== What is this wiki? ==
This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]
* [[Using VMware Player to run Linux training]]
* [[Issues running python on Linux]]
* [[Error Initialize GIT git init --initial-branch=main]]
* [[repo issue "def print(self, *args, **kwargs):"]]
* [[Replacement for command ldd on Linux]]
* [[Optimal swap size for building with Yocto Project]]
* [[Linux Network Managers and Configuration Files]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Best hardware to build Yocto Project]]
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://git.yoctoproject.org/ Yocto source Repositories]
* [http://layers.openembedded.org OpenEmbedded layers index]
* [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]
* [[Directories and installation variables]]
* [[How to add libstdc++ to a Yocto (Poky) image]]
* [[How to run a script at boot automatically]]
* [[How to run a systemd script at boot automatically]]
* [[Create patches using quilt]]
* [[Building Software from an External Source]]
* [[opkg command options]]
* [[Managing RDEPENDS into a recipe]]
* [[Extract the list of packages into a Yocto image]]
* [[Toaster setup and usage]]
* [[Python assignment operators]]
* [[Skip connectivity checks]]
* [[Set default root password]]
* [[Yocto package management]]
* [[Yocto build on a cluster with IceCC]]
* [[Add native gcc to the target image]]
* [[List IPK package depencencies]]
* [[Yocto Project what I wish I'd known]]
* [[Using devtool to modify recipes in Yocto]]
* [[How to include uEnv.txt in Yocto image]]
* [[Add build information into a Yocto image]]
* [[Add a systemd service file into a Yocto image]]
* [[Yocto Project licenses for LIC_FILES_CHKSUM]]
* [[Set Proprietary license for a recipe]]
* [[Yocto sstate usage summary to the build]]
* [[Upgrade to Yocto honister 3.4]]
* [[Override syntax change from Yocto honister 3.4]]
* [[Modify the linux kernel with configuration fragments in Yocto]]
* [[Add a debug banner in a Yocto recipe]]
* [[How to trace a variable setting with bitbake-getvar]]
* [[How to detect the Yocto version using bitbake]]
* [[Support other languages and keyboards than English in Yocto]]
* [[List the files shipped by your recipe]]
* [[How to run CVE checks using the Yocto Project]]
* [[How to add binary files via a custom recipe]]
* [[How to configure network using systemd-networkd in Yocto]]
* [[Yocto Project override operators]]
* [[How to generate an initrd image with Yocto]]

Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]

== Linux kernel ==
* [[Kernel message logging with printk]]

== C/C++ userspace ==
* [[Manage the GPIO lines in C with libgpiod]]

== Microsoft .NET and Mono ==
* [[Embedded Linux .NET applications with Yocto]]

== Qt ==
* [[Install Qt 5 on Ubuntu]]

== Hardware and SBC ==
* [[iMX6 definitive GPIO guide]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]
* [[How to Shrink a VirtualBox Virtual Machine]]

== About us ==
* [https://koansoftware.com/company/ Who we are]

== DISCLAIMER ==

'''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY

All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''

MediaWiki:Common.css

2025-11-01T14:43:16Z

Admin:

MediaWiki:Common.css

2025-11-01T14:42:11Z

Admin:

/* CSS placed here will be applied to all skins */

body {
font-family: "Arial", "Helvetica", sans-serif !important;
}

a {
color: #911017;
}

a:visited {
color: #911017;
}

a.new,
#p-personal a.new {
color: #cc2200;
}

MediaWiki:Common.css

2025-11-01T14:40:30Z

Admin: force font

/* CSS placed here will be applied to all skins */

body {
font: Arial, Helvetica, sans-serif !important;
}

a {
color: #911017;
}

a:visited {
color: #911017;
}

a.new,
#p-personal a.new {
color: #cc2200;
}

MediaWiki:Common.css

2025-11-01T14:36:42Z

Admin:

/* CSS placed here will be applied to all skins */

body {
font: Arial,Helvetica,sans-serif;
}

a {
color: #911017;
}

a:visited {
color: #911017;
}

a.new,
#p-personal a.new {
color: #cc2200;
}

MediaWiki:Common.css

2025-11-01T14:35:47Z

Admin: add koan customization

/* CSS placed here will be applied to all skins */

body {
font: x-small Geneva,Arial,Helvetica,sans-serif;
}

a {
color: #911017;
}

a:visited {
color: #911017;
}

a.new,
#p-personal a.new {
color: #cc2200;
}

Main Page

2025-11-01T14:32:23Z

Admin: spaces

Welcome on [https://koansoftware.com Koan Software] official wiki

== KOAN Embedded Software Engineering ==

[https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.

== What is this wiki? ==
This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]
* [[Using VMware Player to run Linux training]]
* [[Issues running python on Linux]]
* [[Error Initialize GIT git init --initial-branch=main]]
* [[repo issue "def print(self, *args, **kwargs):"]]
* [[Replacement for command ldd on Linux]]
* [[Optimal swap size for building with Yocto Project]]
* [[Linux Network Managers and Configuration Files]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Best hardware to build Yocto Project]]
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://git.yoctoproject.org/ Yocto source Repositories]
* [http://layers.openembedded.org OpenEmbedded layers index]
* [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]
* [[Directories and installation variables]]
* [[How to add libstdc++ to a Yocto (Poky) image]]
* [[How to run a script at boot automatically]]
* [[How to run a systemd script at boot automatically]]
* [[Create patches using quilt]]
* [[Building Software from an External Source]]
* [[opkg command options]]
* [[Managing RDEPENDS into a recipe]]
* [[Extract the list of packages into a Yocto image]]
* [[Toaster setup and usage]]
* [[Python assignment operators]]
* [[Skip connectivity checks]]
* [[Set default root password]]
* [[Yocto package management]]
* [[Yocto build on a cluster with IceCC]]
* [[Add native gcc to the target image]]
* [[List IPK package depencencies]]
* [[Yocto Project what I wish I'd known]]
* [[Using devtool to modify recipes in Yocto]]
* [[How to include uEnv.txt in Yocto image]]
* [[Add build information into a Yocto image]]
* [[Add a systemd service file into a Yocto image]]
* [[Yocto Project licenses for LIC_FILES_CHKSUM]]
* [[Set Proprietary license for a recipe]]
* [[Yocto sstate usage summary to the build]]
* [[Upgrade to Yocto honister 3.4]]
* [[Override syntax change from Yocto honister 3.4]]
* [[Modify the linux kernel with configuration fragments in Yocto]]
* [[Add a debug banner in a Yocto recipe]]
* [[How to trace a variable setting with bitbake-getvar]]
* [[How to detect the Yocto version using bitbake]]
* [[Support other languages and keyboards than English in Yocto]]
* [[List the files shipped by your recipe]]
* [[How to run CVE checks using the Yocto Project]]
* [[How to add binary files via a custom recipe]]
* [[How to configure network using systemd-networkd in Yocto]]
* [[Yocto Project override operators]]
* [[How to generate an initrd image with Yocto]]

Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]

== Linux kernel ==
* [[Kernel message logging with printk]]

== C/C++ userspace ==
* [[Manage the GPIO lines in C with libgpiod]]

== Microsoft .NET and Mono ==
* [[Embedded Linux .NET applications with Yocto]]

== Qt ==
* [[Install Qt 5 on Ubuntu]]

== Hardware and SBC ==
* [[iMX6 definitive GPIO guide]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]
* [[How to Shrink a VirtualBox Virtual Machine]]

== About us ==
* [https://koansoftware.com/company/ Who we are]

== DISCLAIMER ==

'''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY

All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''

Extract the list of packages into a Yocto image

2018-10-08T12:45:10Z

Admin: Created page with "== Extract the list of packages into an image of Yocto Project / Openembedded == The old way bitbake -g <image> && cat pn-depends.dot | grep -v -e '-native' | grep -v digra..."

== Extract the list of packages into an image of Yocto Project / Openembedded ==

The old way

bitbake -g <image> && cat pn-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq

Or the newer way

bitbake -g <image> && cat pn-buildlist | grep -ve "native" | sort | uniq

Link : https://community.nxp.com/docs/DOC-94953

Main Page

2018-10-08T12:42:47Z

Admin: /* Yocto Project */

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

'''KaeilOS(R) is a registered trademark of KOAN sas - Bergamo, ITALY

All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' 
 

== KOAN Embedded Software Engineering ==

[http://koansoftware.com KOAN] è una software house italiana, specializzata in soluzioni software Linux embedded e real time su piattaforme RISC della famiglia ARM (Raspberry, Atmel, Freescale, NXP).
Fondata nel 1996 da esperienze diversificate, KOAN è un'azienda italiana con sede a Bergamo, operante nel settore del terziario avanzato che si propone come fornitore di sistemi software embedded per automazione industriale, telecomunicazioni, automotive, meccatronica e aerospaziale.

== What is KaeilOS ==
KaeilOS was an OpenSource software framework based on OpenEmbedded to create GNU/Linux distributions aimed for embedded devices developed by KOAN from 2004 to 2010.

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]
* [[Using VMware Player to run Linux training]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://git.yoctoproject.org/ Yocto source Repositories]
* [http://layers.openembedded.org OpenEmbedded layers index]
* [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]
* [[Directories and installation variables]]
* [[How to add libstdc++ to a Yocto (Poky) image]]
* [[How to run a script at boot automatically]]
* [[Create patches using quilt]]
* [[Building Software from an External Source]]
* [[opkg command options]]
* [[Managing RDEPENDS into a recipe]]
* [[Extract the list of packages into a Yocto image]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [http://koansoftware.com/en/content/profile Who we are]

Managing RDEPENDS into a recipe

2018-07-25T13:31:12Z

Admin:

== Managing RDEPENDS into a recipe with Yocto Project / Openembedded ==

If you need to add a shared library into a final image you have to use the RDEPENDS keyword into the recipe.
Although the official Yocto Project / Openembedded documentation state that you have to use a simple RDEPENDS keyword specifying the name of the package providing quch library, in some cases you need to specify the '-lib' version of the package providing the library.

For example using 'ncurses' you could expect to use this syntax

RDEPENDS_${PN} = "ncurses"

which will get you only these files

$ tar tjvf core-image-minimal-qemuarm.tar.bz2 | grep -i ncurses
-rw-r--r-- root/root 645 2018-07-25 10:48 ./var/lib/opkg/info/ncurses-terminfo-base.control
-rw-r--r-- root/root 685 2018-07-25 10:48 ./var/lib/opkg/info/ncurses.control
-rw-r--r-- root/root 514 2018-07-25 10:48 ./var/lib/opkg/info/ncurses-terminfo-base.list
-rw-r--r-- root/root 142 2018-07-25 10:48 ./var/lib/opkg/info/ncurses.list

but actually you need to specify this

RDEPENDS_${PN} = "ncurses-libncurses"

that gives you what needed

$ tar tjvf core-image-minimal-qemuarm.tar.bz2 | grep -i ncurses
-rwxr-xr-x root/root 116932 2018-07-25 10:47 ./lib/libncurses.so.5.9
lrwxrwxrwx root/root 0 2018-07-25 10:47 ./lib/libncurses.so.5 -> libncurses.so.5.9
-rw-r--r-- root/root 645 2018-07-25 12:24 ./var/lib/opkg/info/ncurses-terminfo-base.control
-rw-r--r-- root/root 402 2018-07-25 12:24 ./var/lib/opkg/info/libncurses5.control
-rw-r--r-- root/root 44 2018-07-25 12:24 ./var/lib/opkg/info/libncurses5.list
-rwxr-xr-x root/root 90 2018-07-25 12:24 ./var/lib/opkg/info/libncurses5.postinst
-rw-r--r-- root/root 514 2018-07-25 12:24 ./var/lib/opkg/info/ncurses-terminfo-base.list

Opkg command options

2018-05-13T07:38:13Z

Admin: /* Install packages via internet */

[http://code.google.com/p/opkg/ OPKG] (short for '''O'''pen '''P'''ac'''K'''a'''G'''e Management) is a leightweight [http://en.wikipedia.org/wiki/Package_management_system package management system] for [https://en.wikipedia.org/wiki/Embedded_system embedded systems]. OPKG is a fork of [[IPKG (en)|IPKG]].)

The package management in the shell is a powerful tool, and offers many possibilities.

This article explains how to search / install / remove packages and some more interesting commands which offers OPKG. If you want to learn all options of OPKG, enter following command in the [[Shell (en)|Terminal]]:

opkg

== Install packages via internet ==
To be able to install a package, the [http://en.wikipedia.org/wiki/Software_repository feed] defined in the '''/etc/opkg''', should be updated. If this is not done, the installation will be terminated with the error message: '''Unknown package''' ..... Always enter the following command before installing:

opkg update

{{Warnung|Be careful when integrating 3rd party package feeds. If the feed is not available, or not maintained correctly, upgrading the firmware or installing packages will fail!}}

=== Installation ===
The installation of a package is done with the following command:

opkg install $package_name

=== Search package ===
There are different ways to search a package. First of all the package management offers the option '''search''', but unfortunately this option doesn't work quite well.

opkg list | grep search_term

It's also possible to use an asterisk symbol as wildcard in the search term.

opkg list *webadmin*

=== Deinstallation ===
Removing a package is done like this:

opkg remove $package_name

== Install local packages ==
Uupdate the package lists, this way the dependencies (if required) for the package will be resolved and installed. The command is:

opkg update

=== Installation of one package ===
Use the following command for the installation.

opkg install /tmp/$file_name_of_the_package

=== Installation of multiple packages ===
The installation of multiple packages is also easy, once all files are copied with [[FTP (en)|FTP]] in the directory
opkg install /tmp/*.ipk

=== Deinstallation ===
The removal of a package is also done with the package name (without the version and the extention ipk) and the following command:

opkg remove $package_name

== Other interesting commands ==

=== Update sources ===
'''Always''' update the sources before any package manipulation (e.g. installation, search, download of packages), with the command:

opkg update

=== Upgrade Firmware ===
With the following command it's possible to install all available updates for your Dreambox.

opkg upgrade

=== Chain commands ===
With two "and" symbols (&&) it's possible to chain commands. This way the second command is executed, as soon as the first is succesfully performed. The following command is very often used, to update the sources and the firmware.

opkg update && opkg upgrade

=== Install multiple packages from the feeds ===

opkg install $package_name $package_name $package_name $package_name

=== Deinstall multiplpe packages ===

opkg remove $package_name $package_name $package_name $package_name

=== Show all available packages from the feeds ===

opkg list

=== Show all installed packages ===

opkg list-installed

=== Show installed package ===
The following command can be used to search for an installed package. If the package is installed the name is shown with the version number. If no output is displayed, the package is not installed ot the name of the package is wrong.

opkg list-installed $package_name

=== Show upgradable packages ===

opkg list-upgradable

=== Show packages page by page ===
Packages can be shown with the command <code>[http://en.wikipedia.org/wiki/More_%28command%29 more]</code>. Use the {{Taste|space}} or {{Taste|↵ Enter}} to continue.

opkg list | more
opkg list-installed | more
opkg list-upgradable | more

=== Install packages from a website ===
Packages can be installed directly from a web adress, e.g. with following command.

opkg install http://www.yyy.com/zzzz/$package_name.ipk

=== Download package from the feed ===

opkg download $package_name

=== Show package information ===

opkg info $package_name

=== Show package dependencies ===
Lists packages which are '''mandatory''' for an installation.

opkg depends $package_name

=== Show packages which require the package as dependency ===
Shows the packages which have the <code>$package_name</code> as required dependency.

opkg whatdepends $package_name

=== Simulate package installation ===
Loads the package and simulates the installation. Ideal to check if an installation would be performed succesfully.

opkg --noaction $package_name

=== Deinstall package with all dependencies ===
Removes a package and all installed dependencies.

opkg --autoremove $package_name

=== Set package on hold ===
Prevent an update of a package (using the flag <code>'''hold'''</code>).

opkg flag hold $package_name

=== Release package ===
Release a package which is on '''<code>hold</code>'''.

opkg flag user $package_name

=== List the compatible package architectures ===
Shows the content of the file <code>/etc/opkg/arch.conf</code>.

opkg print-architecture

== Tips and Tricks ==

=== Proxy Server ===
When using a [http://en.wikipedia.org/wiki/Proxy_server Proxy Server] to install packages, edit the configuration file <code>/etc/opkg/opkg.conf</code>. The entries should be self explaining ;)

=== Unpack IPK packages ===
Packages can be unpacked on a home computer. With Linux no extra tools are required, for Windows users the programm [http://www.7-zip.org/ 7-Zip] can be used. And for MAC users [http://macitbetter.com/ BetterZIP].

=== Write text file with list of installed packages ===
With following command it's possible to create a list of installed packages, and write the list in a text file.

The list with the name '''e2plugins''' can be found in the directory <code>/home/root</code>. This file can be used to show the installed packages, and reinstall the plugins after a new image was flashed. Of course you have to copy the list from the Dreambox on your computer (e.g. using [[FTP (en)|FTP]]).

opkg list-installed *extensions* | awk '{ print $1 }' > /home/root/e2plugins

Install the content of the list is possible with following command. Make sure the text file is in the directory <code>/home/root</code>. And of course the packages should be available on the feeds.

opkg update && opkg install $(cat /home/root/e2plugins)

An other method to install multiple packages is described in the chapter [[OPKG (en)#Install multiple packages from the feeds|other interesting commands]]. But you need to know the names of the packages.

opkg update && opkg install $paketname $paketname $paketname $paketname

Opkg command options

2018-05-08T19:52:00Z

Admin: Created page with "[http://code.google.com/p/opkg/ OPKG] (short for '''O'''pen '''P'''ac'''K'''a'''G'''e Management) is a leightweight [http://en.wikipedia.org/wiki/Package_management_system pac..."

[http://code.google.com/p/opkg/ OPKG] (short for '''O'''pen '''P'''ac'''K'''a'''G'''e Management) is a leightweight [http://en.wikipedia.org/wiki/Package_management_system package management system] for [https://en.wikipedia.org/wiki/Embedded_system embedded systems]. OPKG is a fork of [[IPKG (en)|IPKG]].)

The package management in the shell is a powerful tool, and offers many possibilities.

This article explains how to search / install / remove packages and some more interesting commands which offers OPKG. If you want to learn all options of OPKG, enter following command in the [[Shell (en)|Terminal]]:

opkg

== Install packages via internet ==
To be able to install a package, the [http://en.wikipedia.org/wiki/Software_repository feed] defined in the <code>/etc/opkg</code>, should be updated. If this is not done, the installation will be terminated with the error message: <code>Unknown package ....</code>. Always enter the following command before installing:
<syntaxhighlight>
opkg update
</syntaxhighlight>

{{Warnung|Be careful when integrating 3rd party package feeds. If the feed is not available, or not maintained correctly, upgrading the firmware or installing packages will fail!}}

=== Installation ===
The installation of a package is done with the following command:

opkg install $package_name

=== Search package ===
There are different ways to search a package. First of all the package management offers the option '''search''', but unfortunately this option doesn't work quite well.

opkg list | grep search_term

It's also possible to use an asterisk symbol as wildcard in the search term.

opkg list *webadmin*

=== Deinstallation ===
Removing a package is done like this:

opkg remove $package_name

== Install local packages ==
Uupdate the package lists, this way the dependencies (if required) for the package will be resolved and installed. The command is:

opkg update

=== Installation of one package ===
Use the following command for the installation.

opkg install /tmp/$file_name_of_the_package

=== Installation of multiple packages ===
The installation of multiple packages is also easy, once all files are copied with [[FTP (en)|FTP]] in the directory
opkg install /tmp/*.ipk

=== Deinstallation ===
The removal of a package is also done with the package name (without the version and the extention ipk) and the following command:

opkg remove $package_name

== Other interesting commands ==

=== Update sources ===
'''Always''' update the sources before any package manipulation (e.g. installation, search, download of packages), with the command:

opkg update

=== Upgrade Firmware ===
With the following command it's possible to install all available updates for your Dreambox.

opkg upgrade

=== Chain commands ===
With two "and" symbols (&&) it's possible to chain commands. This way the second command is executed, as soon as the first is succesfully performed. The following command is very often used, to update the sources and the firmware.

opkg update && opkg upgrade

=== Install multiple packages from the feeds ===

opkg install $package_name $package_name $package_name $package_name

=== Deinstall multiplpe packages ===

opkg remove $package_name $package_name $package_name $package_name

=== Show all available packages from the feeds ===

opkg list

=== Show all installed packages ===

opkg list-installed

=== Show installed package ===
The following command can be used to search for an installed package. If the package is installed the name is shown with the version number. If no output is displayed, the package is not installed ot the name of the package is wrong.

opkg list-installed $package_name

=== Show upgradable packages ===

opkg list-upgradable

=== Show packages page by page ===
Packages can be shown with the command <code>[http://en.wikipedia.org/wiki/More_%28command%29 more]</code>. Use the {{Taste|space}} or {{Taste|↵ Enter}} to continue.

opkg list | more
opkg list-installed | more
opkg list-upgradable | more

=== Install packages from a website ===
Packages can be installed directly from a web adress, e.g. with following command.

opkg install http://www.yyy.com/zzzz/$package_name.ipk

=== Download package from the feed ===

opkg download $package_name

=== Show package information ===

opkg info $package_name

=== Show package dependencies ===
Lists packages which are '''mandatory''' for an installation.

opkg depends $package_name

=== Show packages which require the package as dependency ===
Shows the packages which have the <code>$package_name</code> as required dependency.

opkg whatdepends $package_name

=== Simulate package installation ===
Loads the package and simulates the installation. Ideal to check if an installation would be performed succesfully.

opkg --noaction $package_name

=== Deinstall package with all dependencies ===
Removes a package and all installed dependencies.

opkg --autoremove $package_name

=== Set package on hold ===
Prevent an update of a package (using the flag <code>'''hold'''</code>).

opkg flag hold $package_name

=== Release package ===
Release a package which is on '''<code>hold</code>'''.

opkg flag user $package_name

=== List the compatible package architectures ===
Shows the content of the file <code>/etc/opkg/arch.conf</code>.

opkg print-architecture

== Tips and Tricks ==

=== Proxy Server ===
When using a [http://en.wikipedia.org/wiki/Proxy_server Proxy Server] to install packages, edit the configuration file <code>/etc/opkg/opkg.conf</code>. The entries should be self explaining ;)

=== Unpack IPK packages ===
Packages can be unpacked on a home computer. With Linux no extra tools are required, for Windows users the programm [http://www.7-zip.org/ 7-Zip] can be used. And for MAC users [http://macitbetter.com/ BetterZIP].

=== Write text file with list of installed packages ===
With following command it's possible to create a list of installed packages, and write the list in a text file.

The list with the name '''e2plugins''' can be found in the directory <code>/home/root</code>. This file can be used to show the installed packages, and reinstall the plugins after a new image was flashed. Of course you have to copy the list from the Dreambox on your computer (e.g. using [[FTP (en)|FTP]]).

opkg list-installed *extensions* | awk '{ print $1 }' > /home/root/e2plugins

Install the content of the list is possible with following command. Make sure the text file is in the directory <code>/home/root</code>. And of course the packages should be available on the feeds.

opkg update && opkg install $(cat /home/root/e2plugins)

An other method to install multiple packages is described in the chapter [[OPKG (en)#Install multiple packages from the feeds|other interesting commands]]. But you need to know the names of the packages.

opkg update && opkg install $paketname $paketname $paketname $paketname

Main Page

2018-05-08T15:06:40Z

Admin: /* Yocto Project */

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

'''KaeilOS(R) is a registered trademark of KOAN sas - Bergamo, ITALY

All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' 
 

== KOAN Embedded Software Engineering ==

[http://koansoftware.com KOAN] è una software house italiana, specializzata in soluzioni software Linux embedded e real time su piattaforme RISC della famiglia ARM (Raspberry, Atmel, Freescale, NXP).
Fondata nel 1996 da esperienze diversificate, KOAN è un'azienda italiana con sede a Bergamo, operante nel settore del terziario avanzato che si propone come fornitore di sistemi software embedded per automazione industriale, telecomunicazioni, automotive, meccatronica e aerospaziale.

== What is KaeilOS ==
KaeilOS was an OpenSource software framework based on OpenEmbedded to create GNU/Linux distributions aimed for embedded devices developed by KOAN from 2004 to 2010.

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]
* [[Using VMware Player to run Linux training]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://git.yoctoproject.org/ Yocto source Repositories]
* [http://layers.openembedded.org OpenEmbedded layers index]
* [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]
* [[Directories and installation variables]]
* [[How to add libstdc++ to a Yocto (Poky) image]]
* [[How to run a script at boot automatically]]
* [[Create patches using quilt]]
* [[Building Software from an External Source]]
* [[opkg command options]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [http://koansoftware.com/en/content/profile Who we are]

Yocto Project my own quick start

2018-04-29T09:29:44Z

Admin: /* Edit the configuration files */

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-2018 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 [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html 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 libsdl1.2-dev xterm

== Development Code - branch 2.4 'rocko' ==

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 rocko

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

poky/
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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

Yocto Project my own quick start

2018-04-29T09:27:04Z

Admin: /* Starting the QEMU Emulator */

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-2018 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 [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html 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 libsdl1.2-dev xterm

== Development Code - branch 2.4 'rocko' ==

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 rocko

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

poky/
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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 ?= "qemuxarm"
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

Yocto Project my own quick start

2018-04-29T09:24:48Z

Admin: /* Starting the QEMU Emulator */

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-2018 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 [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html 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 libsdl1.2-dev xterm

== Development Code - branch 2.4 'rocko' ==

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 rocko

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

poky/
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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 ?= "qemuxarm"
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

== Building cross-compiler ==

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

$ bitbake meta-toolchain

Yocto Project my own quick start

2018-04-29T09:24:39Z

Admin: /* Starting the QEMU Emulator */

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-2018 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 [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html 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 libsdl1.2-dev xterm

== Development Code - branch 2.4 'rocko' ==

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 rocko

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

poky/
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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 ?= "qemuxarm"
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 qemuxarm

== Building cross-compiler ==

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

$ bitbake meta-toolchain

Yocto Project my own quick start

2018-04-29T09:24:28Z

Admin: /* Edit the configuration files */

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-2018 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 [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html 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 libsdl1.2-dev xterm

== Development Code - branch 2.4 'rocko' ==

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 rocko

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

poky/
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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
├── documentation
├── LICENSE
├── meta
├── meta-openembedded
├── meta-poky
├── meta-selftest
├── meta-skeleton
├── meta-yocto-bsp
├── oe-init-build-env
├── README.hardware -> meta-yocto-bsp/README.hardware
├── README.LSB
├── 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 ?= "qemuxarm"
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 qemux86

== Building cross-compiler ==

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

$ bitbake meta-toolchain

Building Software from an External Source

2017-11-09T13:26:16Z

Admin:

== Building Software from an External Source using Yocto Project / Openembedded ==

I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that?

By default, the OpenEmbedded build system uses the Build Directory when building source code. The build process involves fetching the source files, unpacking them, and then patching them if necessary before the build takes place.

Situations exist where you might want to build software from source files that are external to and thus outside of the OpenEmbedded build system. For example, suppose you have a project that includes a new BSP with a heavily customized kernel. And, you want to minimize exposing the build system to the development team so that they can focus on their project and maintain everyone's workflow as much as possible. In this case, you want a kernel source directory on the development machine where the development occurs. You want the recipe's SRC_URI variable to point to the external directory and use it as is, not copy it.

in this case use the externalsrc class - you can inherit this in the original bb recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

Depending on the type of build (eg, 'inherit module' for out of tree Linux kernel modules) you may or may not need to set EXTERNALSRC_BUILD.

inherit externalsrc
EXTERNALSRC = "/some/path"
EXTERNALSRC_BUILD = "/some/path"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

Building Software from an External Source

2017-11-09T12:58:08Z

Admin:

== Building Software from an External Source using Yocto Project / Openembedded ==

I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that?

By default, the OpenEmbedded build system uses the Build Directory when building source code. The build process involves fetching the source files, unpacking them, and then patching them if necessary before the build takes place.

Situations exist where you might want to build software from source files that are external to and thus outside of the OpenEmbedded build system. For example, suppose you have a project that includes a new BSP with a heavily customized kernel. And, you want to minimize exposing the build system to the development team so that they can focus on their project and maintain everyone's workflow as much as possible. In this case, you want a kernel source directory on the development machine where the development occurs. You want the recipe's SRC_URI variable to point to the external directory and use it as is, not copy it.

in this case use the externalsrc class - you can inherit this in the original bb recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

Building Software from an External Source

2017-11-09T12:56:14Z

Admin:

== Building Software from an External Source using Yocto Project / Openembedded ==

By default, the OpenEmbedded build system uses the Build Directory when building source code. The build process involves fetching the source files, unpacking them, and then patching them if necessary before the build takes place.

Situations exist where you might want to build software from source files that are external to and thus outside of the OpenEmbedded build system. For example, suppose you have a project that includes a new BSP with a heavily customized kernel. And, you want to minimize exposing the build system to the development team so that they can focus on their project and maintain everyone's workflow as much as possible. In this case, you want a kernel source directory on the development machine where the development occurs. You want the recipe's SRC_URI variable to point to the external directory and use it as is, not copy it.

To build from software that comes from an external source, all you need to do is inherit the externalsrc class and then set the EXTERNALSRC variable to point to your external source code. Here are the statements to put in your local.conf file:

INHERIT += "externalsrc"
EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree" # change only myrecipe with your name

Source : http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc

Alternatively if it's more permanent, use the externalsrc class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

Building Software from an External Source

2017-11-09T12:55:44Z

Admin:

== Building Software from an External Source using Yocto Project / Openembedded ==

By default, the OpenEmbedded build system uses the Build Directory when building source code. The build process involves fetching the source files, unpacking them, and then patching them if necessary before the build takes place.

Situations exist where you might want to build software from source files that are external to and thus outside of the OpenEmbedded build system. For example, suppose you have a project that includes a new BSP with a heavily customized kernel. And, you want to minimize exposing the build system to the development team so that they can focus on their project and maintain everyone's workflow as much as possible. In this case, you want a kernel source directory on the development machine where the development occurs. You want the recipe's SRC_URI variable to point to the external directory and use it as is, not copy it.

To build from software that comes from an external source, all you need to do is inherit the externalsrc class and then set the EXTERNALSRC variable to point to your external source code. Here are the statements to put in your local.conf file:

INHERIT += "externalsrc"
EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree"

Source : http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc

Alternatively if it's more permanent, use the externalsrc class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

Building Software from an External Source

2017-11-09T12:51:07Z

Admin:

== Building Software from an External Source using Yocto Project / Openembedded ==

By default, the OpenEmbedded build system uses the Build Directory when building source code. The build process involves fetching the source files, unpacking them, and then patching them if necessary before the build takes place.

Situations exist where you might want to build software from source files that are external to and thus outside of the OpenEmbedded build system. For example, suppose you have a project that includes a new BSP with a heavily customized kernel. And, you want to minimize exposing the build system to the development team so that they can focus on their project and maintain everyone's workflow as much as possible. In this case, you want a kernel source directory on the development machine where the development occurs. You want the recipe's SRC_URI variable to point to the external directory and use it as is, not copy it.

To build from software that comes from an external source, all you need to do is inherit the externalsrc class and then set the EXTERNALSRC variable to point to your external source code. Here are the statements to put in your local.conf file:

INHERIT += "externalsrc"
EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree"

Source : http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc

Building Software from an External Source

2017-11-09T12:50:31Z

Admin: Created page with "== Building Software from an External Source using Yocto Project / Openembedded == By default, the OpenEmbedded build system uses the Build Directory when building source cod..."

Main Page

2017-11-09T12:48:22Z

Admin: /* Yocto Project */

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

== '''All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' ==
 

== What is KaeilOS ==
KaeilOS is an OpenSource software framework to create GNU/Linux distributions aimed for embedded devices. Primarily, the project maintains and develops a collection of BitBake recipes. The bitbakes consist of the source URL of the package, dependencies and compile or install options.
During the build process they are used to track dependencies, cross-compile the package and pack it up, suitable to be installed on the target device. It's also possible to create complete images, consisting of root file system and kernel. As a first step the framework will build a cross-compiler toolchain for the target platform.
Currently the project is no longer active as independent system but is using Yocto Project at its place.

KaeilOS runs in a lot of different plaftforms ([http://en.wikipedia.org/wiki/x86 x86], [http://en.wikipedia.org/wiki/Powerpc PowerPC] and [http://en.wikipedia.org/wiki/ARM_architecture ARM]) and includes more than 7000 opensource packages and libraries suitable for:
* Embedded system
* Desktop
* Server

== Getting Started ==
* [[Required packages]]
* [[Build environment]]
* [[Run KaeilOS on QEmu]]

== Development ==
* [[Optimization proposal]]
* [[New ideas]]
* [https://trello.com/b/djLUmKKL '''KaeilOS''' Task Tracking with Trello]

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[2.6.x Kernel Compilation Problems]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]
* [[Using VMware Player to run Linux training]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://www.openembedded.org/wiki/LayerIndex Yocto layers index]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]
* [[Directories and installation variables]]
* [[How to add libstdc++ to a Yocto (Poky) image]]
* [[How to run a script at boot automatically]]
* [[Create patches using quilt]]
* [[Building Software from an External Source]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [[ Who we are ]]
* [[ KaeilOS services and community ]]

Using VMware Player to run Linux training

2017-01-18T14:31:48Z

Admin: /* Using VMware Player to run Linux crashes with Ubuntu 16.04 as Host */

== Using VMware Player to run Linux crashes with Ubuntu 16.04 as Host ==

I'm using VMware Player and have Ubuntu 16.04 as Host.
When I launch VMware 12.5.2 it crashes.

Launching vmplayer from the command line I get this error:
E105: PANIC: VERIFY bora\vmcore\vmx\main\timeTracker_user.c:238 bugNr=148722

[SOLVED] VMware CPU speed problem
fix the issue in your '''/etc/vmware/config''' file,
you have to add:

host.cpukHz = "2500000"
host.noTSC = "TRUE"
ptsc.noTSC = "TRUE"

where "X" is your CPU speed. I have a 2.5 GHz P4, so mine is 2500000.

cat /proc/cpuinfo | grep 'model name'
model name : Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz

Using VMware Player to run Linux training

2017-01-18T14:30:35Z

Admin: Created page with " == Using VMware Player to run Linux crashes with Ubuntu 16.04 as Host == I'm using VMware Player and have Ubuntu 16.04 as Host. When I launch VMware 12.5.2 it crashes. Lau..."

== Using VMware Player to run Linux crashes with Ubuntu 16.04 as Host ==

I'm using VMware Player and have Ubuntu 16.04 as Host.
When I launch VMware 12.5.2 it crashes.

Launching vmplayer from the command line I get this error:
E105: PANIC: VERIFY bora\vmcore\vmx\main\timeTracker_user.c:238 bugNr=148722

[SOLVED] VMware CPU speed problem
fix the issue in your '''/etc/vmware/config''' file,
you have to add:

host.cpukHz = "2500000"
host.noTSC = "TRUE"
ptsc.noTSC = "TRUE"

where "X" is your CPU speed. I have a 2.5 GHz P4, so mine is 2500000.
model name : Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz

Main Page

2017-01-18T14:28:37Z

Admin: /* Problem solving - Howto */

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

== '''All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' ==
 

== What is KaeilOS ==
KaeilOS is an OpenSource software framework to create GNU/Linux distributions aimed for embedded devices. Primarily, the project maintains and develops a collection of BitBake recipes. The bitbakes consist of the source URL of the package, dependencies and compile or install options.
During the build process they are used to track dependencies, cross-compile the package and pack it up, suitable to be installed on the target device. It's also possible to create complete images, consisting of root file system and kernel. As a first step the framework will build a cross-compiler toolchain for the target platform.
Currently the project is no longer active as independent system but is using Yocto Project at its place.

KaeilOS runs in a lot of different plaftforms ([http://en.wikipedia.org/wiki/x86 x86], [http://en.wikipedia.org/wiki/Powerpc PowerPC] and [http://en.wikipedia.org/wiki/ARM_architecture ARM]) and includes more than 7000 opensource packages and libraries suitable for:
* Embedded system
* Desktop
* Server

== Getting Started ==
* [[Required packages]]
* [[Build environment]]
* [[Run KaeilOS on QEmu]]

== Development ==
* [[Optimization proposal]]
* [[New ideas]]
* [https://trello.com/b/djLUmKKL '''KaeilOS''' Task Tracking with Trello]

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[2.6.x Kernel Compilation Problems]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]
* [[Using VMware Player to run Linux training]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://www.openembedded.org/wiki/LayerIndex Yocto layers index]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [[ Who we are ]]
* [[ KaeilOS services and community ]]

Yocto Project my own quick start

2016-10-19T14:19:56Z

Admin: /* Edit the configuration files */

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-2013 Linux Foundation]

== The 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.
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:

$ sudo dpkg-reconfigure dash

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

The following list shows the required packages by function given a supported Ubuntu Linux distribution:

* Essentials: Packages needed to build an image on a headless system:

$ 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:

$ sudo apt-get install libsdl1.2-dev xterm

* Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals:

$ sudo apt-get install make xsltproc docbook-utils fop

* ADT Installer Extras: Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer:

$ sudo apt-get install autoconf automake libtool libglib2.0-dev

== BitBake requires Python 2.7.3 or later ==

BitBake requires Python 2.7.3 or later 
If you have Ubuntu older that 12.04 LTS you have to install Python 2.7.5 manually

sudo apt-get install libreadline5-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev

wget http://www.python.org/ftp/python/2.7.5/Python-2.7.5.tar.bz2
tar xjvf Python-2.7.5.tar.bz2
cd Python-2.7.5

./configure
make
sudo make install

python -V

== Development Code (branch jethro 2.0) ==

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 jethro

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

.
└── poky
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-hob
├── meta-skeleton
├── meta-yocto
├── meta-yocto-bsp
├── oe-init-build-env
├── README
├── README.hardware
└── scripts

Download the Freescale layers:

$ cd $HOME/yocto/poky
$ git clone git://git.yoctoproject.org/meta-fsl-arm -b jethro
$ git clone https://github.com/Freescale/meta-fsl-arm-extra.git -b jethro

Download the Qt5 layer (if necessary):

$ cd $HOME/yocto/poky
$ git clone https://github.com/meta-qt5/meta-qt5.git -b jethro

== 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
├── documentation
├── LICENSE
├── meta
├── meta-fsl-arm
├── meta-fsl-arm-extra
├── meta-hob
├── meta-skeleton
├── meta-yocto
├── meta-yocto-bsp
├── oe-init-build-env
├── README
├── README.hardware
└── scripts

== Edit the configuration files ==

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

BBLAYERS ?= " \
/home/tux/yocto/poky/meta \
/home/tux/yocto/poky/meta-yocto \
/home/tux/yocto/poky/meta-yocto-bsp \
/home/tux/yocto/poky/meta-openembedded/meta-oe \
/home/tux/yocto/poky/meta-fsl-arm \
/home/tux/yocto/poky/meta-fsl-arm-extra \
"

or if use Qt5

BBLAYERS ?= " \
/home/tux/yocto/poky/meta \
/home/tux/yocto/poky/meta-yocto \
/home/tux/yocto/poky/meta-yocto-bsp \
/home/tux/yocto/poky/meta-openembedded/meta-oe \
/home/tux/yocto/poky/meta-fsl-arm \
/home/tux/yocto/poky/meta-fsl-arm-extra \
/home/tux/yocto/poky/meta-qt5 \
/home/tux/yocto/poky/meta-openembedded/meta-ruby \
/home/tux/yocto/poky/meta-openembedded/meta-multimedia \
"

Remembed to edit also $HOME/yocto/poky/build/conf/local.conf

== Building the Image ==

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

$ runqemu qemux86 tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-minimal-qemux86.ext3

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.

Yocto Project my own quick start

2016-10-19T14:19:26Z

Admin: /* Edit the configuration files */

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-2013 Linux Foundation]

== The 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.
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:

$ sudo dpkg-reconfigure dash

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

The following list shows the required packages by function given a supported Ubuntu Linux distribution:

* Essentials: Packages needed to build an image on a headless system:

$ 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:

$ sudo apt-get install libsdl1.2-dev xterm

* Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals:

$ sudo apt-get install make xsltproc docbook-utils fop

* ADT Installer Extras: Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer:

$ sudo apt-get install autoconf automake libtool libglib2.0-dev

== BitBake requires Python 2.7.3 or later ==

BitBake requires Python 2.7.3 or later 
If you have Ubuntu older that 12.04 LTS you have to install Python 2.7.5 manually

sudo apt-get install libreadline5-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev

wget http://www.python.org/ftp/python/2.7.5/Python-2.7.5.tar.bz2
tar xjvf Python-2.7.5.tar.bz2
cd Python-2.7.5

./configure
make
sudo make install

python -V

== Development Code (branch jethro 2.0) ==

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 jethro

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

.
└── poky
├── bitbake
├── documentation
├── LICENSE
├── meta
├── meta-hob
├── meta-skeleton
├── meta-yocto
├── meta-yocto-bsp
├── oe-init-build-env
├── README
├── README.hardware
└── scripts

Download the Freescale layers:

$ cd $HOME/yocto/poky
$ git clone git://git.yoctoproject.org/meta-fsl-arm -b jethro
$ git clone https://github.com/Freescale/meta-fsl-arm-extra.git -b jethro

Download the Qt5 layer (if necessary):

$ cd $HOME/yocto/poky
$ git clone https://github.com/meta-qt5/meta-qt5.git -b jethro

== 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
├── documentation
├── LICENSE
├── meta
├── meta-fsl-arm
├── meta-fsl-arm-extra
├── meta-hob
├── meta-skeleton
├── meta-yocto
├── meta-yocto-bsp
├── oe-init-build-env
├── README
├── README.hardware
└── scripts

== Edit the configuration files ==

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

BBLAYERS ?= " \
/home/tux/yocto/poky/meta \
/home/tux/yocto/poky/meta-yocto \
/home/tux/yocto/poky/meta-yocto-bsp \
/home/tux/yocto/poky/meta-openembedded/meta-oe \
/home/tux/yocto/poky/meta-fsl-arm \
/home/tux/yocto/poky/meta-fsl-arm-extra \
"

or if use Qt5

BBLAYERS ?= " \
/home/tux/yocto/poky/meta \
/home/tux/yocto/poky/meta-yocto \
/home/tux/yocto/poky/meta-yocto-bsp \
/home/tux/yocto/poky/meta-openembedded/meta-oe \
/home/tux/yocto/poky/meta-fsl-arm \
/home/tux/yocto/poky/meta-fsl-arm-extra \
/home/tux/yocto/poky/meta-qt5 \
/home/tux/yocto/poky/meta-openembedded/meta-ruby \
/home/tux/yocto/poky/meta-openembedded/meta-multimedia \
"

== Building the Image ==

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

$ runqemu qemux86 tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-minimal-qemux86.ext3

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.

Main Page

2016-09-12T13:16:55Z

Admin:

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

== '''All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' ==
 

== What is KaeilOS ==
KaeilOS is an OpenSource software framework to create GNU/Linux distributions aimed for embedded devices. Primarily, the project maintains and develops a collection of BitBake recipes. The bitbakes consist of the source URL of the package, dependencies and compile or install options.
During the build process they are used to track dependencies, cross-compile the package and pack it up, suitable to be installed on the target device. It's also possible to create complete images, consisting of root file system and kernel. As a first step the framework will build a cross-compiler toolchain for the target platform.
Currently the project is no longer active as independent system but is using Yocto Project at its place.

KaeilOS runs in a lot of different plaftforms ([http://en.wikipedia.org/wiki/x86 x86], [http://en.wikipedia.org/wiki/Powerpc PowerPC] and [http://en.wikipedia.org/wiki/ARM_architecture ARM]) and includes more than 7000 opensource packages and libraries suitable for:
* Embedded system
* Desktop
* Server

== Getting Started ==
* [[Required packages]]
* [[Build environment]]
* [[Run KaeilOS on QEmu]]

== Development ==
* [[Optimization proposal]]
* [[New ideas]]
* [https://trello.com/b/djLUmKKL '''KaeilOS''' Task Tracking with Trello]

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[2.6.x Kernel Compilation Problems]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://www.openembedded.org/wiki/LayerIndex Yocto layers index]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [[ Who we are ]]
* [[ KaeilOS services and community ]]

Main Page

2016-09-09T12:42:00Z

Admin: /* DISCLAIMER */

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

== '''All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' ==
 

== What is KaeilOS ==
KaeilOS is an OpenSource software framework to create GNU/Linux distributions aimed for embedded devices. Primarily, the project maintains and develops a collection of BitBake recipes. The bitbakes consist of the source URL of the package, dependencies and compile or install options. During the build process they are used to track dependencies, cross-compile the package and pack it up, suitable to be installed on the target device. It's also possible to create complete images, consisting of root file system and kernel. As a first step the framework will build a cross-compiler toolchain for the target platform.

KaeilOS runs in a lot of different plaftforms ([http://en.wikipedia.org/wiki/x86 x86], [http://en.wikipedia.org/wiki/Powerpc PowerPC] and [http://en.wikipedia.org/wiki/ARM_architecture ARM]) and includes more than 7000 opensource packages and libraries suitable for:
* Embedded system
* Desktop
* Server

== Getting Started ==
* [[Required packages]]
* [[Build environment]]
* [[Run KaeilOS on QEmu]]

== Development ==
* [[Optimization proposal]]
* [[New ideas]]
* [https://trello.com/b/djLUmKKL '''KaeilOS''' Task Tracking with Trello]

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[2.6.x Kernel Compilation Problems]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://www.openembedded.org/wiki/LayerIndex Yocto layers index]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [[ Who we are ]]
* [[ KaeilOS services and community ]]

Main Page

2016-09-09T12:41:50Z

Admin: /* All contents of this website are released under the Creative Commons Attribution-ShareAlike 3.0 Unported License */

Welcome on [http://www.kaeilos.com KaeilOS] official wiki

== DISCLAIMER ==

== '''All contents of this website are released under the
[http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]''' ==
 

== What is KaeilOS ==
KaeilOS is an OpenSource software framework to create GNU/Linux distributions aimed for embedded devices. Primarily, the project maintains and develops a collection of BitBake recipes. The bitbakes consist of the source URL of the package, dependencies and compile or install options. During the build process they are used to track dependencies, cross-compile the package and pack it up, suitable to be installed on the target device. It's also possible to create complete images, consisting of root file system and kernel. As a first step the framework will build a cross-compiler toolchain for the target platform.

KaeilOS runs in a lot of different plaftforms ([http://en.wikipedia.org/wiki/x86 x86], [http://en.wikipedia.org/wiki/Powerpc PowerPC] and [http://en.wikipedia.org/wiki/ARM_architecture ARM]) and includes more than 7000 opensource packages and libraries suitable for:
* Embedded system
* Desktop
* Server

== Getting Started ==
* [[Required packages]]
* [[Build environment]]
* [[Run KaeilOS on QEmu]]

== Development ==
* [[Optimization proposal]]
* [[New ideas]]
* [https://trello.com/b/djLUmKKL '''KaeilOS''' Task Tracking with Trello]

== Problem solving - Howto ==
* [[FAQ]]
* [[Setup NFS root filesystem]]
* [[2.6.x Kernel Compilation Problems]]
* [[Setup an external toolchain with Yocto]]
* [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]

== Openembedded Core ==
* [[Submit patches to Openembedded]]
* [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]
* [[OE-Core Standalone Setup]]

== Openembedded Debugging ==
* [[Openembedded debugging]]
* [[Packages information list]]

== Yocto Project ==
* [[Yocto Project my own quick start]]
* [[Yocto versus Poky versus Angstrom]]
* [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]
* [http://www.openembedded.org/wiki/LayerIndex Yocto layers index]
* [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]
* [[OE/Yocto prebuilt toolchains]]
* [[Howto build a kernel module out of the kernel tree]]
* [[Howto speed up Yocto build]]
* [[bitbake options]]

== Documents ==
* [[ARM cores list]]
* [[systemd vs sysvinit]]
* [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]
* [[Development with VMware]]

== About us ==
* [[ Who we are ]]
* [[ KaeilOS services and community ]]

File:Koala transparent.png

2013-10-04T18:08:23Z

Admin:

MediaWiki:Sidebar

2013-10-01T18:57:08Z

Admin:

MediaWiki:Sidebar

2013-09-26T16:45:13Z

Admin:

* navigation
** mainpage|mainpage-description
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES
* Licenza
** http://creativecommons.org/licenses/by-sa/3.0/|Content is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

MediaWiki:Sidebar

2013-09-26T16:40:11Z

Admin:

* navigation
** mainpage|mainpage-description
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES
* Licenza
** Co http://creativecommons.org/licenses/by-sa/3.0/|Content is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

MediaWiki:Sidebar

2013-09-26T16:39:45Z

Admin:

MediaWiki:Sidebar

2013-09-26T16:38:19Z

Admin:

MediaWiki:Sidebar

2013-09-26T16:37:40Z

Admin:

MediaWiki:Sidebar

2013-09-26T16:36:40Z

Admin:

MediaWiki:Sidebar

2013-09-26T16:35:29Z

Admin:

MediaWiki:Sidebar

2013-09-26T16:34:51Z

Yocto Project my own quick start

2012-10-31T08:19:59Z

Admin:

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]

== The 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.
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:

$ sudo dpkg-reconfigure dash

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

== Development Code ==

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

$ git clone git://git.yoctoproject.org/poky.git

== Initializing the Build 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

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.

== 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.

== 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.

$ runqemu qemux86 tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-minimal-qemux86.ext3

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.

Yocto Project my own quick start

2012-10-29T16:46:11Z

Admin:

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]

== The 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.
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:

$ sudo dpkg-reconfigure dash

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

== Initializing the Build 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

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.

== 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.

== 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.

$ runqemu qemux86 tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/core-image-minimal-qemux86.ext3

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.

Yocto Project my own quick start

2012-10-29T15:57:31Z

Admin:

Yocto Project my own quick start

2012-10-29T15:57:10Z

Admin:

Yocto Project my own quick start

2012-10-29T15:56:47Z

Admin:

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-2011 Linux Foundation]

== The 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.
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:

$ sudo dpkg-reconfigure dash

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

== Initializing the Build 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

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.

== 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.

Yocto Project my own quick start

2012-10-29T15:56:03Z

Admin: /* Building the Image */

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]

== The 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.
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:

$ sudo dpkg-reconfigure dash

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

== Initializing the Build 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

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.

== 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.