summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-09-02 11:54:20 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-09-02 23:38:52 +0100
commit99cb233e0c8058c9a406e18fedae70b0f60e3864 (patch)
tree46d8754ec8d2d0c96a963c314d68819ec1387d3b /documentation/yocto-project-qs
parentce0456d95d9859477429a1208433245ae8724fd7 (diff)
downloadpoky-99cb233e0c8058c9a406e18fedae70b0f60e3864.tar.gz
YOCTO #1088: documentation - Added text to partially address package bug
This bug was filed by Gary Thomas and was requesting more information on the "hows" and "whys" of setting up your own package repositories. At this point, I have added information to help the user understand build performance issues when choosing between the RPM and IPKG packaging systems. Likely, there is more that needs to be added to fully address this bug. For now, I added explanations in the packaging class and glossary areas of the YP reference manual, a new paragraph in the YP QS just prior to firing off a build, and a new bit of information in the configuring PMS in the ADT Manual. (From yocto-docs rev: d0025f862cb85ca741787b4737dca286e3ebfb45) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml16
1 files changed, 15 insertions, 1 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 62280b619f..c95e1a02ab 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -330,7 +330,8 @@
330 <filename>conf/local.conf</filename> file.</para></listitem> 330 <filename>conf/local.conf</filename> file.</para></listitem>
331 </itemizedlist> 331 </itemizedlist>
332 <para> 332 <para>
333 Take some time to examine your <filename>conf/local.conf</filename> file. 333 Take some time to examine your <filename>conf/local.conf</filename> file found in the
334 Yocto Project file's <filename>conf</filename>.
334 The defaults should work fine. 335 The defaults should work fine.
335 However, if you have a multi-core CPU you might want to set the variable 336 However, if you have a multi-core CPU you might want to set the variable
336 BB_NUMBER_THREADS equal to twice the number of processor cores your system has. 337 BB_NUMBER_THREADS equal to twice the number of processor cores your system has.
@@ -338,6 +339,19 @@
338 Setting these variables can significantly shorten your build time. 339 Setting these variables can significantly shorten your build time.
339 By default, these variables are commented out. 340 By default, these variables are commented out.
340 </para> 341 </para>
342
343 <para>
344 Another consideration before you build is the package manager used when creating
345 the image.
346 By default, the Yocto Project build system uses the RPM package manager.
347 You can control this configuration by using the
348 <filename><ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#var-PACKAGE_CLASSES'>PACKAGE_CLASSES</ulink></filename> variable.
349 For additional package manager selection information, see
350 <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink> in
351 <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
352 The Yocto Project Reference Manual</ulink>.
353 </para>
354
341 <para> 355 <para>
342 Continue with the following command to build an OS image for the target, which is 356 Continue with the following command to build an OS image for the target, which is
343 <filename>core-image-sato</filename> in this example. 357 <filename>core-image-sato</filename> in this example.