Changes between Version 9 and Version 10 of OSSIEBeagleboard_BitBake

Timestamp:

02/17/11 13:51:49 (2 years ago)

Author:

jawil06

Comment:

Revised initial setup instructions. Building OSSIE section still needs work.

OSSIEBeagleboard_BitBake

@@ -6 +6 @@
 [[PageOutline]]
 == Getting Started With !OpenEmbedded ==
-Note: If you have already set up !OpenEmbedded and would just like to !BitBake OSSIE you may skip to the Building OSSIE section.
+Note: If you have already set up !OpenEmbedded and would just like to !BitBake OSSIE you may skip to the [http://ossie.wireless.vt.edu/trac/wiki/OSSIEBeagleboard_BitBake#BuildingOSSIE Building OSSIE] section.
 
-Note: This section is adopted from the !OpenEmbedded Wiki: [http://wiki.openembedded.org/index.php/Getting_started].
+Note: This section is adopted from the !OpenEmbedded Wiki: [http://wiki.openembedded.org/index.php/Getting_started OE Getting Started]. Please read [http://www.openembedded.org/index.php/OEandYourDistro OE and Your Distro] for advice on how to configure your operating system.
 
 === Prerequisites ===
-Before starting, make sure you have the following before preceding (see your distributions documentation on how to install software):
+Before starting, make sure you have the following software before preceding (see your distributions documentation on how to install software):
     1. Git
     2. SVN
+    3. CVS
+    4. C++ Compiler (e.g. g++)
+    5. diffstat
+    6. texi2html
+    7. GNU Autotools (specifically autoconf, automake and libtool)
+    8. makeinfo
+    9. chrpath
+    10. qemu (may not be necessary on some systems)
 
+Other software may be required, but most distributions already include it.
 
 === Getting The Toolchain ===
 First, create your directory structure. I recommend creating an OE directory in your home folder:
 {{{
-$ mkdir -p $HOME/OE/build/conf
-$ cd $HOME/OE
+mkdir -p $HOME/OE/build/conf
+cd $HOME/OE
 }}}
 
 Now, get the lastest !BitBake (1.10.1 as of this writing, to find the latest version visit http://download.berlios.de/bitbake/), and unpack it:
 {{{
-$ wget http://download.berlios.de/bitbake/bitbake-1.10.1.tar.gz # Download the BitBake package
-$ tar zxvf bitbake-1.10.1.tar.gz                                # Extract it
-$ mv bitbake{-1.10.1,}                                          # Rename the directory to bitbake
+wget http://download.berlios.de/bitbake/bitbake-1.10.1.tar.gz # Download the BitBake package
+tar zxvf bitbake-1.10.1.tar.gz                                # Extract it
+mv bitbake{-1.10.1,}                                          # Rename the directory to bitbake
 }}}
 
-Now that we have !BitBake, we need to get !OpenEmbedded. Before simply checking out !OpenEmbedded trunk, let's look for a recently tested tag here: http://git.openembedded.org/cgit.cgi/openembedded/refs/tags. As of this writing, the newest tested tag is "tested_2010-10-29". Be sure to check the commit log to ensure that a "beagleboard angstrom-2008.1" build was at least tested with a simple console-image. To get !OpenEmdedd run (this may take a while depending on your connection speed):
+Now that we have !BitBake, we need to get !OpenEmbedded. Before simply checking out !OpenEmbedded trunk, let's look for a recently tested tag (or even better, a recent release) here: http://git.openembedded.org/cgit.cgi/openembedded/refs/tags. As of this writing, the newest tested tag is "tested_2010-10-29". Be sure to check the commit log to ensure that a "beagleboard angstrom-2008.1" build was at least tested with a simple console-image. To get !OpenEmdedd run (this may take a while depending on your connection speed):
 {{{
-$ git clone git://git.openembedded.org/openembedded
-$ cd openembedded
+git clone git://git.openembedded.org/openembedded
+cd openembedded
 # Replace "tested_2010-10-29" with the tag/branch you want
-$ git checkout tested_2010-10-29
+git checkout tested_2010-10-29
 }}}
 
@@ -41 +50 @@
 Before configuring !BitBake, we should set some environment variables. There are many places to do this, including at build time, but we recommend placing the following lines at the end of your .bashrc file:
 {{{
-$ cat >> $HOME/.bashrc << EOF
+cat >> $HOME/.bashrc << EOF
+
 # OpenEmbedded Environment Setup
-export OEBASE=$HOME/OE
-export PATH=$OEBASE/bitbake/bin:$PATH
-export BBPATH=$OEBASE/build:$OEBASE/openembedded
+export OEBASE=\$HOME/OE
+export PATH=\$OEBASE/bitbake/bin:\$PATH
+export BBPATH=\$OEBASE/build:\$OEBASE/openembedded
 export BB_ENV_EXTRAWHITE="OEBASE"
 EOF
-$ . $HOME/.bashrc # Update environment
+. $HOME/.bashrc # Update environment
 }}}
 
@@ -55 +65 @@
 Now that we have the toolchain and OSSIE recipes, we need to set up our configuration. Copy a sample configuration and edit it to fit our needs:
 {{{
-$ cd $HOME/OE/
-$ cp openembedded/conf/local.conf.sample build/conf/local.conf
-$ vim build/conf/local.conf # Use your favorite text-editor
+cd $HOME/OE/
+cp openembedded/conf/local.conf.sample build/conf/local.conf
+vim build/conf/local.conf # Use your favorite text-editor
 }}}
 
@@ -80 +90 @@
 DISTRO = "angstrom-2008.1"
 ...
+# These lines may be necessary depending on your build system
+ENABLE_BINARY_LOCALE_GENERATION = "0"
+ASSUME_PROVIDED += "qemu-native"
+GLIBC_GENERATE_LOCALES = "en_US.UTF-8" # Add any locales you may need
+...
 IMAGE_FSTYPES = " tar.bz2 "
 ...
@@ -85 +100 @@
 }}}
 
-Other options that may be of interest are PARALLEL_MAKE and BB_NUMBER_THREADS especially for multi-core or multi-processor build systems.
+Other options that may be of interest are PARALLEL_MAKE and BB_NUMBER_THREADS especially for multi-threaded, multi-core and/or multi-processor build systems.
 
 === Building a Console Image ===
 This step is not required but recommended to ensure that your setup is working properly before you try to build the OSSIE recipes. We will build task-base and console-image. For more information on what exactly is happening here, see the !OpenEmbedded documentation. Together, these can take hours on a standard machine. We recommend you let it run over night.
 {{{
-$ cd $HOME/OE/build
-$ bitbake task-base && bitbake console-image
+cd $OEBASE/build
+bitbake task-base && bitbake console-image
 }}}
 If both builds succeed (run the bitbake command again to ensure success) then you will have a kernel image located at: [[br]]
@@ -103 +118 @@
 The OSSIE recipes are located in the OSSIE SVN repository.
 {{{
-$ cd $HOME/OE/
-$ svn --username anon --password ossiesdr co \
+cd $OEBASE
+svn --username anon --password ossiesdr co \
   https://ossie.wireless.vt.edu/repos/ossie/ossiedev/branches/jawil06/recipes ossie-recipes
 }}}
-Note: if you skipped the instructions on setting up !OpenEmbedded, you must add ossie-recipes to BBFILES in your local.conf.
+Note: if you skipped the instructions on setting up !OpenEmbedded, you must add ossie-recipes to the BBFILES variable in your local.conf.
 
 === omniORBpy Workarounds ===
@@ -114 +129 @@
 First, modify the omniORB-native recipe to stage all of the necessary header files:
 {{{
-$ vim $OEHOME/openembedded/recipes/omniorb/omniorb_4.1.4.bb # Use your favorite text-editor
+vim $OEBASE/openembedded/recipes/omniorb/omniorb_4.1.4.bb # Use your favorite text-editor
 # Add the following to the bottom of the file
 TODO: what needs to be added?
@@ -121 +136 @@
 Finally, !BitBake the modified recipe.
 {{{
-$ cd $OEHOME/build
-$ bitbake omniorb-native # This could take some time
+cd $OEBASE/build
+bitbake omniorb-native # This could take some time
 }}}
 
@@ -128 +143 @@
 This will create a console image with all the necessary development files to build other OSSIE components and tools for which there is not already a recipe natively on the !BeagleBoard
 {{{
-$ cd $HOME/OE/build
-$ bitbake ossie-dev-console-image
+cd $OEBASE/build
+bitbake ossie-dev-console-image
 }}}