From 50021cba20a09b1ed685db5466f940b17d4880ac Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 20 Apr 2011 14:20:19 +0100 Subject: Drop documentation directory, this is replaced by the new yocto-docs repository --- documentation/adt-manual/adt-package.xml | 82 -------------------------------- 1 file changed, 82 deletions(-) delete mode 100644 documentation/adt-manual/adt-package.xml (limited to 'documentation/adt-manual/adt-package.xml') diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml deleted file mode 100644 index fc2a1a0cb..000000000 --- a/documentation/adt-manual/adt-package.xml +++ /dev/null @@ -1,82 +0,0 @@ - - - -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. - - -
- 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 - . - - -
- -
- 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. - - - As an example, consider a scenario where you are using OPKG and you want to add - the libglade package to sysroot. - - - 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 - - - - 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 - - -
- - -- cgit v1.2.3