diff options
| author |   Chris Larson <clarson@kergoth.com> | 2004-07-01 23:29:02 +0000 |
|---|---|---|
| committer | Chris Larson <clarson@kergoth.com> | 2004-07-01 23:29:02 +0000 |
| commit | d2328aea13b0df12ca72da15acafa47d612cf20a (patch) | |
| tree | ee98f4bc61fe9f9e5d5aeaa2852f419630be2036 | |
| parent | 916eadd83a3d3b8990baf8d22c9bfbdcfbe2c2f8 (diff) | |
| download | bitbake-contrib-d2328aea13b0df12ca72da15acafa47d612cf20a.tar.gz | |
Kill off old unmaintained docs.
| -rw-r--r-- | doc/README | 62 |
1 files changed, 1 insertions, 61 deletions
diff --git a/doc/README b/doc/README index 37567c47a..038d07177 100644 --- a/doc/README +++ b/doc/README @@ -1,61 +1 @@ -OpenEmbedded Build Infrastructure README --- - -Project overview: - -(Note, the following is a high-level blurb, initial pass, -which may refer to functionality that does not yet exist, but will -by the time said blurb is advertised as fact.) - -OpenEmbedded is a full-featured development environment allowing -users to target a wide variety of devices. Supporing multiple -build, release paths, and configurations, OpenEmbedded extends the -capabilities of your build and release engineers. OpenEmbedded -uses compilation and configuration caching at most levels to improve -developer efficiency. - -Basic operation: - -At its simplist, OpenEmbedded is a metadata management system, and -multiple tools that make use of said data. What this comes down to, -is a set of tools that manage builds and deployment in a single place, -regardless of what target device, operating system, or packaging system -we're building for. - -Assuming that you already have a .oe file or set of .oe files to utilize, -the following applies: - -First, unless you installed an OE rpm, deb, or ipk, you'll want to set OEDIR -to point to the OE repository that contains classes/ and bin/oe/. - - cd oe - OEDIR=`pwd` - export OEDIR - -Next, for convenience, you'll want to add OEDIR/bin to your path. - - PATH=$PATH:$OEDIR/bin - -Then, unless you're building natively (for the same architecture and operating -system as you are building from), you'll want to customize conf/local.conf within -the directory you'll be buliding from. - - cd packages - echo 'TARGET_ARCH=arm' >> conf/local.conf - -Finally, you can start the build. There are a few ways to do so. First, you -can run 'oebuild' on a single OE. Second, you can run oemake, which operates -on an existing set of metadata, and will follow build dependencies. - - oebuild content/glibc_2.3.2.oe - -or- - export OEFILES=`pwd`/content/*.oe - oemake glibc_2.3.2 - -Please see the other files in doc/, as well as the --help output for each of the OE -commands, for further details on the capabilities and use of the system. - -Thanks, - -Chris Larson - kergoth at handhelds dot org -Embedded Linux Developer - clarson at ti dot com +See the oe-doc repository and openembedded.org. |