/usr/local/src/yocto/meta-yocto \
/usr/local/src/yocto/meta-yocto-bsp \
/usr/local/src/yocto/meta-myarm \
- "
-
- BBLAYERS_NON_REMOVABLE ?= " \
- /usr/local/src/yocto/meta \
- /usr/local/src/yocto/meta-yocto \
"
</literallayout>
Adding the layer to this file allows the build system to build the BSP and
Features, updates and known issues for the current
release of the Yocto Project.
</para></listitem>
- <listitem><para><emphasis>
- <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink>:</emphasis>
- A graphical user interface for BitBake.
- Hob's primary goal is to enable a user to perform common tasks more easily.
- </para></listitem>
<listitem><para><emphasis>
<ulink url='&YOCTO_HOME_URL;/tools-resources/projects/toaster'>Toaster</ulink>:</emphasis>
An Application Programming Interface (API) and web-based
Toaster provides an efficient interface to the OpenEmbedded build
that allows you to start builds and examine build statistics.
</para></listitem>
- <listitem><para><emphasis>Image Development using Hob:</emphasis>
- You can use the <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink>
- to build custom operating system images within the build
- environment.
- Hob provides an efficient interface to the OpenEmbedded build system.
- </para></listitem>
<listitem><para><emphasis>Using a Development Shell:</emphasis>
You can use a <filename>devshell</filename> to efficiently debug
commands or simply edit packages.
</para>
</section>
-<section id='image-development-using-hob'>
- <title>Image Development Using Hob</title>
-
- <para>
- The <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink> is a graphical user interface for the
- OpenEmbedded build system, which is based on BitBake.
- You can use the Hob to build custom operating system images within the Yocto Project build environment.
- Hob simply provides a friendly interface over the build system used during development.
- In other words, building images with the Hob lets you take care of common build tasks more easily.
- </para>
-
- <para>
- For a better understanding of Hob, see the project page at
- <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'></ulink>
- on the Yocto Project website.
- If you follow the "Documentation" link from the Hob page, you will
- find a short introductory training video on Hob.
- The following lists some features of Hob:
- <itemizedlist>
- <listitem><para>You can setup and run Hob using these commands:
- <literallayout class='monospaced'>
- $ source oe-init-build-env
- $ hob
- </literallayout></para></listitem>
- <listitem><para>You can set the
- <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
- for which you are building the image.</para></listitem>
- <listitem><para>You can modify various policy settings such as the
- package format with which to build,
- the parallelism BitBake uses, whether or not to build an
- external toolchain, and which host to build against.
- </para></listitem>
- <listitem><para>You can manage
- <link linkend='understanding-and-creating-layers'>layers</link>.</para></listitem>
- <listitem><para>You can select a base image and then add extra packages for your custom build.
- </para></listitem>
- <listitem><para>You can launch and monitor the build from within Hob.</para></listitem>
- </itemizedlist>
- </para>
-</section>
-
<section id="platdev-appdev-devshell">
<title>Using a Development Shell</title>
supported Linux distribution, instances might exist where you
encounter a problem while using the Yocto Project on a specific
distribution.
- For example, the CentOS 6.4 distribution does not include the
- Gtk+ 2.20.0 and PyGtk 2.21.0 (or higher) packages, which are
- required to run
- <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink>.
</note>
</section>
reference hardware Board Support Packages (BSPs), respectively:
<filename>meta-yocto</filename> and
<filename>meta-yocto-bsp</filename>.
- When running BitBake or Hob for the first time after upgrading,
+ When running BitBake for the first time after upgrading,
your <filename>conf/bblayers.conf</filename> file will be
updated to handle this change and you will be asked to
re-run or restart for the changes to take effect.
</section>
</section>
- <section id='migration-1.6-directory-layout-changes'>
- <title>Directory Layout Changes</title>
-
- <para>
- The <filename>meta-hob</filename> layer has been removed from
- the top-level of the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
- The contents of this layer are no longer needed by the Hob
- user interface for building images and toolchains.
- </para>
- </section>
-
<section id='migration-1.6-package-test-ptest'>
<title>Package Test (ptest)</title>
-l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS
Show debug logging for the specified logging domains
-P, --profile Profile the command and save reports.
- -u UI, --ui=UI The user interface to use (e.g. knotty, hob, depexp).
+ -u UI, --ui=UI The user interface to use (e.g. knotty and depexp).
-t SERVERTYPE, --servertype=SERVERTYPE
Choose which server to use, process or xmlrpc.
--revisions-changed Set the exit code depending on whether upstream
</para>
</section>
-<section id='ref-classes-packageinfo'>
- <title><filename>packageinfo.bbclass</filename></title>
-
- <para>
- The <filename>packageinfo</filename> class
- gives a BitBake user interface the ability to retrieve information
- about output packages from the <filename>pkgdata</filename> files.
- </para>
-
- <para>
- This class is enabled automatically when using the
- <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink>
- user interface.
- </para>
-</section>
-
<section id='ref-classes-patch'>
<title><filename>patch.bbclass</filename></title>
<para>
Be careful when deleting files in this directory.
You can safely delete old images from this directory (e.g.
- <filename>core-image-*</filename>, <filename>hob-image-*</filename>,
- etc.).
+ <filename>core-image-*</filename>).
However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.),
bootloader and other supplementary files might be deployed here prior to building an
image.
/home/scottrif/poky/meta-yocto \
/home/scottrif/poky/meta-yocto-bsp \
/home/scottrif/poky/meta-mykernel \
- "
-
- BBLAYERS_NON_REMOVABLE ?= " \
- /home/scottrif/poky/meta \
- /home/scottrif/poky/meta-yocto \
"
</literallayout>
- <note>
- The
- <link linkend='var-BBLAYERS_NON_REMOVABLE'><filename>BBLAYERS_NON_REMOVABLE</filename></link>
- variable exists only for
- <ulink url='https://www.yoctoproject.org/tools-resources/projects/hob'>Hob</ulink>.
- The OpenEmbedded build system does not use this
- variable.
- </note>
</para>
<para>
</glossdef>
</glossentry>
- <glossentry id='var-BBLAYERS_NON_REMOVABLE'><glossterm>BBLAYERS_NON_REMOVABLE</glossterm>
- <info>
- BBLAYERS_NON_REMOVABLE[doc] = "Lists core layers that cannot be removed from the bblayers.conf file."
- </info>
- <glossdef>
- <para role="glossdeffirst">
-<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
- Lists core layers that cannot be removed from the
- <filename>bblayers.conf</filename> file during a build
- using the
- <ulink url='https://www.yoctoproject.org/tools-resources/projects/hob'>Hob</ulink>.
- <note>
- When building an image outside of Hob, the OpenEmbedded
- build system ignores this variable.
- </note>
- </para>
-
- <para>
- In order for BitBake to build your image using Hob, your
- <filename>bblayers.conf</filename> file must include the
- <filename>meta</filename> and <filename>meta-yocto</filename>
- core layers.
- Here is an example that shows these two layers listed in
- the <filename>BBLAYERS_NON_REMOVABLE</filename> statement:
- <literallayout class='monospaced'>
- BBLAYERS = " \
- /home/scottrif/poky/meta \
- /home/scottrif/poky/meta-yocto \
- /home/scottrif/poky/meta-yocto-bsp \
- /home/scottrif/poky/meta-mykernel \
- "
-
- BBLAYERS_NON_REMOVABLE ?= " \
- /home/scottrif/poky/meta \
- /home/scottrif/poky/meta-yocto \
- "
- </literallayout>
- </para>
- </glossdef>
- </glossentry>
-
<glossentry id='var-BBMASK'><glossterm>BBMASK</glossterm>
<info>
BBMASK[doc] = "Prevents BitBake from processing specific recipes or recipe append files."
remote build servers.
</para>
- <note>
- <para>
- This release of Toaster does allow you to configure and initiate
- builds.
- However, you cannot use Toaster to customize image recipes, which
- still must either be done by hand or through
- <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>Hob</ulink>.
- As Toaster matures, it eventually will equal and surpass Hob
- functionality, at which time Hob will be deprecated.
- </para>
-
- <para>
- For more information on Hob,
- see the
- "<ulink url='&YOCTO_DOCS_DEV_URL;#image-development-using-hob'>Image Development Using Hob</ulink>"
- section in the Yocto Project Development Manual.
- </para>
- </note>
-
<section id='intro-features'>
<title>Toaster Features</title>
projects / thirdparty / openembedded / openembedded-core-contrib.git / commitdiff
