diff options
| author |   Michael 'Mickey' Lauer <mickey@vanille-media.de> | 2003-11-15 00:50:40 +0000 |
|---|---|---|
| committer | Michael 'Mickey' Lauer <mickey@vanille-media.de> | 2003-11-15 00:50:40 +0000 |
| commit | 61695622884fe8a342240c159a563bab335fb2da (patch) | |
| tree | 7b2b5236f3bbeec2eed267a17ec67ec2a0206f3f /doc | |
| parent | 4968e547bad70ff886aea92c5c59877b0d3b89d8 (diff) | |
| download | bitbake-61695622884fe8a342240c159a563bab335fb2da.tar.gz | |
bring in sync with the facts
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/DEVEL | 8 | ||||
| -rw-r--r-- | doc/README | 4 |
2 files changed, 8 insertions, 4 deletions
@@ -5,9 +5,11 @@ How to add the build of a package to OpenEmbedded (henceforth known as "OE") in a few easy steps! First, you'll want to create the .oe. - vi content/packagename-version.oe + vi content/packagename_version.oe :wq +(Note the underscore separating the packagename and the version.) + Next, we need to add some content. First, define the "SRC_URI" variable to point to the upstream source tarball. SRC_URI:=${GNU_MIRROR}/ncurses/ncurses-5.3.tar.gz @@ -18,6 +20,8 @@ that tarball: (Note: "P" defaults to ${PN}-${PV}, which is package name, and package version, respectively.) +(Also note that S=${WORKDIR}/${P} is automatically set, so you +just need to override, if the package extracts into another directory.) Finally, we need to make some decisions on how to build this. Take a look at the sources. If you see a 'configure.in', @@ -28,7 +32,7 @@ Simply tell the buildsystem that: inherit autotools And attempt a build! - oebuild content/packagename-version.oe + oebuild content/packagename_version.oe If the build either is not autotools based, or deviates from it in any way, you can override any of the steps. For example: diff --git a/doc/README b/doc/README index dec2d2f46..37567c47a 100644 --- a/doc/README +++ b/doc/README @@ -47,10 +47,10 @@ 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 + oebuild content/glibc_2.3.2.oe -or- export OEFILES=`pwd`/content/*.oe - oemake glibc-2.3.2 + 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. |