mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 00:20:08 +00:00
Code Issues Projects Releases Wiki Activity

dev-manual, yocto-project-qs: New section on working with source files.

Browse Source 
Fixes [YOCTO #5566]

For the dev-manual, I created a new section called "Working
with Source Files."  In the section, I cover how to set up mirrors
and also how to pre-fetch source using the bitbake -c fetchall
<target> command.

For the yocto-project-qs, I removed the mirror information in the
"Super User" section, which became redundant with the new section
now in the dev-manual.  I also, removed the fetchall variation of
the bitbake command.  Both areas reference into the new section of
the dev-manual now.

(From yocto-docs rev: f314061e3e752d35ea85ed16a60f7f9292180921)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2014-06-17 15:18:53 +03:00
committed by Richard Purdie
parent 45a1c42e7e
commit d785a16dff
2 changed files with 111 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/dev-manual/dev-manual-common-tasks.xml
+97
View File
@@ -6025,6 +6025,103 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
</section> </section>
</section> </section>
<section id='working-with-source-files'>
<title>Working with Source Files</title>
<para>
The OpenEmbedded build system works with source files located
through the
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
variable.
When you build something using BitBake, a big part of the operation
is locating and downloading all the source tarballs.
For images, downloading all the source for various packages can
take a significant amount of time.
</para>
<para>
This section presents information for working with source
files that can lead to more efficient use of resources and
time.
</para>
<section id='setting-up-effective-mirrors'>
<title>Setting up Effective Mirrors</title>
<para>
As mentioned, a good deal that goes into a Yocto Project
build is simply downloading all of the source tarballs.
Maybe you have been working with another build system
(OpenEmbedded or Angstrom) for which you have built up a
sizable directory of source tarballs.
Or, perhaps someone else has such a directory for which you
have read access.
If so, you can save time by adding statements to your
configuration file so that the build process checks local
directories first for existing tarballs before checking the
Internet.
</para>
<para>
Here is an efficient way to set it up in your
<filename>local.conf</filename> file:
<literallayout class='monospaced'>
SOURCE_MIRROR_URL ?= "file:///home/you/your-download-dir/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
# BB_NO_NETWORK = "1"
</literallayout>
</para>
<para>
In the previous example, the
<ulink url='&YOCTO_DOCS_REF_URL;#var-BB_GENERATE_MIRROR_TARBALLS'><filename>BB_GENERATE_MIRROR_TARBALLS</filename></ulink>
variable causes the OpenEmbedded build system to generate
tarballs of the Git repositories and store them in the
<ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'><filename>DL_DIR</filename></ulink>
directory.
Due to performance reasons, generating and storing these
tarballs is not the build system's default behavior.
</para>
<para>
You can also use the
<ulink url='&YOCTO_DOCS_REF_URL;#var-PREMIRRORS'><filename>PREMIRRORS</filename></ulink>
variable.
For an example, see the variable's glossary entry in the
Yocto Project Reference Manual.
</para>
</section>
<section id='getting-source-files-and-suppressing-the-build'>
<title>Getting Source Files and Suppressing the Build</title>
<para>
Another technique you can use to ready yourself for a
successive string of build operations, is to pre-fetch
all the source files without actually starting a build.
This technique lets you work through any download issues
and ultimately gathers all the source files into your
download directory
<ulink url='&YOCTO_DOCS_REF_URL;#structure-build-downloads'><filename>build/downloads</filename></ulink>,
which is located with
<ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'><filename>DL_DIR</filename></ulink>.
</para>
<para>
Use the following BitBake command form to fetch all the
necessary sources without starting the build:
<literallayout class='monospaced'>
$ bitbake -c fetchall &lt;target&gt;
</literallayout>
This variation of the BitBake command guarantees that you
have all the sources for that BitBake target should you
disconnect from the Internet and want to do the build
later offline.
</para>
</section>
</section>
<section id="building-software-from-an-external-source"> <section id="building-software-from-an-external-source">
<title>Building Software from an External Source</title> <title>Building Software from an External Source</title>
documentation/yocto-project-qs/yocto-project-qs.xml
+14 -54
View File
@@ -895,42 +895,14 @@
<para> <para>
A good deal that goes into a Yocto Project build is simply A good deal that goes into a Yocto Project build is simply
downloading all of the source tarballs. downloading all of the source tarballs.
Maybe you have been working with another build system Steps exist that can help you be more efficient with gathering
(OpenEmbedded or Angstrom) for which you have built up a sizable source files.
directory of source tarballs. For example, you can set up local mirrors that hold your
Or, perhaps someone else has such a directory for which you have source tarballs or you can pre-fetch all your source without
read access. initiating a build until later.
If so, you can save time by adding statements to your For more information, see the
configuration file so that the build process checks local "<ulink url='&YOCTO_DOCS_DEV_URL;#working-with-source-files'>Working with Source Files</ulink>"
directories first for existing tarballs before checking the section in the Yocto Project Development Manual.
Internet.
Here is an efficient way to set it up in your
<filename>local.conf</filename> file:
<literallayout class='monospaced'>
SOURCE_MIRROR_URL ?= "file:///home/you/your-download-dir/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
# BB_NO_NETWORK = "1"
</literallayout>
</para>
<para>
In the previous example, the
<ulink url='&YOCTO_DOCS_REF_URL;#var-BB_GENERATE_MIRROR_TARBALLS'><filename>BB_GENERATE_MIRROR_TARBALLS</filename></ulink>
variable causes the OpenEmbedded build system to generate tarballs
of the Git repositories and store them in the
<ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'><filename>DL_DIR</filename></ulink>
directory.
Due to performance reasons, generating and storing these tarballs
is not the build system's default behavior.
</para>
<para>
You can also use the
<ulink url='&YOCTO_DOCS_REF_URL;#var-PREMIRRORS'><filename>PREMIRRORS</filename></ulink>
variable.
For an example, see the variable's glossary entry in the
Yocto Project Reference Manual.
</para> </para>
</section> </section>
@@ -949,25 +921,13 @@
</para> </para>
<para> <para>
Here are some variations on the build process that could be helpful: By default, BitBake aborts when it encounters an error during
<itemizedlist> the build.
<listitem><para>Fetch all the necessary sources without starting If you want to make sure the build continues even when BitBake
the build: encounters an error, use this variation:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake -c fetchall core-image-minimal
</literallayout>
This variation guarantees that you have all the sources for
that BitBake target should you disconnect from the net and
want to do the build later offline.</para></listitem>
<listitem><para>Specify to continue the build even if BitBake
encounters an error.
By default, BitBake aborts the build when it encounters an
error.
This command keeps a faulty build going:
<literallayout class='monospaced'>
$ bitbake -k core-image-minimal $ bitbake -k core-image-minimal
</literallayout></para></listitem> </literallayout>
</itemizedlist>
</para> </para>
<para> <para>