From 2e3d29d493d6a3be006e80e75e41a0ff9ad29564 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 15 Mar 2011 08:08:29 -0600 Subject: documentation/adt-manual/adt-package.xml: Initial file This file is the initial XML file for the chapter on optionally customizing the development packages installation. Signed-off-by: Scott Rifenbark --- documentation/adt-manual/adt-package.xml | 105 +++++++++++++++++++------------ 1 file changed, 65 insertions(+), 40 deletions(-) diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml index 6139442ab..fc2a1a0cb 100644 --- a/documentation/adt-manual/adt-package.xml +++ b/documentation/adt-manual/adt-package.xml @@ -2,55 +2,80 @@ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> +Optionally Customizing the Development Packages Installation + + Because the Yocto Project is suited for embedded Linux development it is + likely that you will need to customize your development packages installation. + For example, if you are developing a minimal image then you might not need + certain packages (e.g. graphics support packages). + Thus, you would like to be able to remove those packages from your sysroot. + -Yocto Project Kernel Architecture and Use Manual +
+ Package Management Systems + + The Yocto Project supports the generation of root filesystem files using + three different Package Management Systems (PMS): + + OPKG – A less well known PMS whose use + originated in the OpenEmbedded and OpenWrt embedded Linux projects. + This PMS works with files packaged in an .ipk format. + See for more + information about OPKG. + RPM – A more widely known PMS intended for GNU/Linux + distributions. + This PMS works with files packaged in an .rms format. + The Yocto Project currently installs through this PMS by default. + See + for more information about RPM. + Debian – The PMS for Debian-based systems + is built on many PMS tools. + The lower-level PMS tool dpkg forms the base of the Debian PMS. + For information on dpkg see + . + + +
-
- Introduction +
+ Configuring the PMS + + Whichever PMS you are using you need to be sure that the + PACKAGE_CLASSES variable in the conf/local.conf + file is set to reflect that system. + The first value you choose for the variable specifies the package file format for the root + filesystem. + Additional values specify additional formats for convenience or testing. + See the configuration file for details. + - The Yocto Project presents the kernel as a fully patched, history-clean git - repository. - The git tree represents the selected features, board support, - and configurations extensively tested by Yocto Project. - The Yocto Project kernel allows the end user to leverage community - best practices to seamlessly manage the development, build and debug cycles. + As an example, consider a scenario where you are using OPKG and you want to add + the libglade package to sysroot. - This manual describes the Yocto Project kernel by providing information - on its history, organization, benefits, and use. - The manual consists of two sections: - - Concepts - Describes concepts behind the kernel. - You will understand how the kernel is organized and why it is organized in - the way it is. You will understand the benefits of the kernel's organization - and the mechanisms used to work with the kernel and how to apply it in your - design process. - Using the Kernel - Describes best practices and "how-to" information - that lets you put the kernel to practical use. Some examples are "How to Build a - Project Specific Tree", "How to Examine Changes in a Branch", and "Saving Kernel - Modifications." - + First, you should generate the ipk file for the libglade package and add it + into a working opkg repository. + Use these commands: + + $ bitbake libglade + $ bitbake package-index + - For more information on the kernel, see the following links: - - - - - - - You can find more information on Yocto Project by visiting the website at - . - + Next, source the environment setup script. + Follow that by setting up the installation destination to point to your + sysroot as <sysroot dir>. + Finally, have an opkg configuration file <conf file> + that corresponds to the opkg repository you have just created. + The following command forms should now work: + + $ opkg-cl –f <conf file> -o <sysroot dir> update + $ opkg-cl –f <conf file>> -o <sysroot dir> --force-overwrite install libglade + $ opkg-cl –f <conf file> -o <sysroot dir> --force-overwrite install libglade-dbg + $ opkg-cl –f <conf file> -o <sysroot dir> --force-overwrite install libglade-dev +
- - - - - - -