From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173005pub.verizon.net ([206.46.173.5]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1OHJYS-0004PC-4s for openembedded-devel@lists.openembedded.org; Wed, 26 May 2010 18:34:05 +0200 Received: from gandalf.denix.org ([unknown] [71.255.238.44]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0L31007SOCH0JE1K@vms173005.mailsrvcs.net> for openembedded-devel@lists.openembedded.org; Wed, 26 May 2010 11:29:30 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id CB46214AF60; Wed, 26 May 2010 12:29:23 -0400 (EDT) Date: Wed, 26 May 2010 12:29:23 -0400 From: Denys Dmytriyenko To: openembedded-devel@lists.openembedded.org Message-id: <20100526162923.GD23464@denix.org> References: <1274879375-19626-1-git-send-email-chase.maupin@ti.com> MIME-version: 1.0 In-reply-to: <1274879375-19626-1-git-send-email-chase.maupin@ti.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-SA-Exim-Connect-IP: 206.46.173.5 X-SA-Exim-Mail-From: denis@denix.org X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Cc: Chase Maupin Subject: Re: [PATCHv2 1/7] common_use_cases: Fix documentation errors X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 May 2010 16:34:05 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Wed, May 26, 2010 at 08:09:29AM -0500, Chase Maupin wrote: > * Fixed up typos and other errors in the documentation. > > Signed-off-by: Chase Maupin Acked-by: Denys Dmytriyenko > --- > docs/usermanual/chapters/common_use_cases.xml | 45 +++++++++++++----------- > 1 files changed, 24 insertions(+), 21 deletions(-) > > diff --git a/docs/usermanual/chapters/common_use_cases.xml b/docs/usermanual/chapters/common_use_cases.xml > index 7ae3ee5..d86d0ca 100644 > --- a/docs/usermanual/chapters/common_use_cases.xml > +++ b/docs/usermanual/chapters/common_use_cases.xml > @@ -7,11 +7,12 @@ > > Creating a new distribution is not complicated, however we urge you > to try existing distributions first, because it's also very easy to do > - wrong. The config need to be created in /conf/distro directory. So what > - has to be inside? > + wrong. The config needs to be created in $OEBASE/openembedded/conf/distro > + directory. So what has to be inside? > + > > DISTRO_VERSION so users will know which > - version of distribution they use. > + version of the distribution they are using. > > > > @@ -71,29 +72,30 @@ SRCDATE = "20061014" >
> Adding a new Machine > > - To be able to build for device OpenEmbedded have to know it, so > - machine config file need to be written. All those configs are stored in > - /conf/machine/ directory. > + To be able to build for a device OpenEmbedded has to know about it, > + so a machine config file needs to be written. All of the machine > + configs are stored in $OEBASE/openembedded/conf/machine/ directory. > > As usual some variables are required: > > - TARGET_ARCH which describe which CPU > - architecture does machine use. > + TARGET_ARCH describes which CPU > + architecture the machine uses. > > > > - MACHINE_FEATURES which describe which > - features device has. More about it in + MACHINE_FEATURES which describes which > + features the device has. More about it in linkend="task-base">task-base section. > > > > PREFERRED_PROVIDER_virtual/kernel has to > - point into proper kernel recipe for this machine. > + point to the proper kernel recipe for this machine. > > > > - Next kernel recipe needs to be added. > + Next the kernel recipe needs to be added if it doesn't already exist. > + >
> >
> @@ -105,7 +107,7 @@ SRCDATE = "20061014" >
> building from unstable source code > Building against the latest, bleeding-edge source has some intricacies of its own. > - For one, it is desirable to pin down a 1 code revision that is known to build to > + For one, it is desirable to pin down a code revision that is known to build to > prevent random breakage in OE at the most inopportune time for all OE users. Here is > how to do that properly. > > @@ -113,7 +115,8 @@ SRCDATE = "20061014" > for cvs: add 'PV = "1.1+cvs${SRCREV}"' to your bb file. > > Accompany either with an entry to conf/distro/include/sane-srcrevs.inc for a revision that you know > - builds successfully. > + builds successfully. It is also common to define the stable SRCREV > + for your package directly in the package recipe. > > > If you really absolutely have to follow the latest commits, you can do that by adding > @@ -126,7 +129,7 @@ SRCDATE = "20061014" >
> Creating your own image > > - Creating own image is easy - only few variables needs to be set: > + Creating own image is easy - only few variables need to be set: > > > IMAGE_BASENAME to give a name for your own > @@ -147,7 +150,7 @@ SRCDATE = "20061014" > IMAGE_LINGUAS is an optional list of > languages which has to be installed into the image > > - Then adding of the image class use: > + Then add the image class using: > > inherit image > And the image recipe is ready for usage. > @@ -240,7 +243,7 @@ export LOCALDIR=$PWD/secret-isv > > > Use source build_source to source the script, > - use env to check that the variable where > + use env to check that the variables were > exported. >
> > @@ -484,8 +487,8 @@ RDEPENDS_${PN} += "\ > Putting it together > In the previous two sections we have prepared the host and > target side. One thing that is missing is combining the two newly > - created tasks and actually create the SDK. This is what we are going > - to do now. > + created tasks and actually creating the SDK. This is what we are > + going to do now. > > Create meta-toolchain-YOU.bb in the > recipes/meta directory and place the following > @@ -529,7 +532,7 @@ SDK_SUFFIX = "toolchain-YOUR" > optional dependencies like directFB, glib-2.0, gstreamer-0.10, tslib > and more esoteric dependencies like mysql and postgres. This allows > developers to simply start developing using Qt and enables system > - integrator to easily recompile Qt and base libraries without tracking > + integrators to easily recompile Qt and base libraries without tracking > down extra dependencies. > > > @@ -575,7 +578,7 @@ $ bitbake meta-toolchain-qte > should start by downloading the SDK and untar it to the root folder > (/). Once this operation is finished you will > find a new directory /usr/local/angstrom/arm/ and > - it contains the environment-setup to setup the > + it contains the environment-setup file to setup the > QMAKESPEC and various other paths. > > > -- > 1.6.0.4 > > > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel