summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2019-03-16 08:02:25 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-03-19 23:54:02 +0000
commit95d6ad04fb681a84722bd32bf568f69da63321e9 (patch)
treefa31d722c431f229fbdde0af46f47f3d04c926e0 /documentation/dev-manual/dev-manual-common-tasks.xml
parentf0d225fcd593dace7f8c383e90038996297c49ba (diff)
downloadpoky-95d6ad04fb681a84722bd32bf568f69da63321e9.tar.gz
dev-manual: Updates to "Replicating Your Build Offline"
I updated the section with some feedback from Richard. This version is much clearer and brings the concepts out a lot better. (From yocto-docs rev: 9790482b9937308bee6aa00a892f50d026187342) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml38
1 files changed, 28 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 8e78a247ce..5f2b6ece3b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -6331,11 +6331,14 @@
6331 It can be useful to take a "snapshot" of upstream sources 6331 It can be useful to take a "snapshot" of upstream sources
6332 used in a build and then use that "snapshot" later to 6332 used in a build and then use that "snapshot" later to
6333 replicate the build offline. 6333 replicate the build offline.
6334 To do so, you need to first prepare and populate your downloads
6335 directory your "snapshot" of files.
6336 Once your downloads directory is ready, you can use it at
6337 any time and from any machine to replicate your build.
6334 </para> 6338 </para>
6335 6339
6336 <para> 6340 <para>
6337 Follow these steps to replicate a build offline by using a 6341 Follow these steps to populate your Downloads directory:
6338 known "snapshot" of source files:
6339 <orderedlist> 6342 <orderedlist>
6340 <listitem><para> 6343 <listitem><para>
6341 <emphasis>Create a Clean Downloads Directory:</emphasis> 6344 <emphasis>Create a Clean Downloads Directory:</emphasis>
@@ -6355,8 +6358,8 @@
6355 INHERIT += "own-mirrors" 6358 INHERIT += "own-mirrors"
6356 BB_GENERATE_MIRROR_TARBALLS = "1" 6359 BB_GENERATE_MIRROR_TARBALLS = "1"
6357 </literallayout> 6360 </literallayout>
6358 During the fetch process, BitBake looks in your mirror 6361 During the fetch process in the next step, BitBake
6359 for source files. 6362 looks in your mirror for source files.
6360 The 6363 The
6361 <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_GENERATE_MIRROR_TARBALLS'><filename>BB_GENERATE_MIRROR_TARBALLS</filename></ulink> 6364 <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_GENERATE_MIRROR_TARBALLS'><filename>BB_GENERATE_MIRROR_TARBALLS</filename></ulink>
6362 variable causes the build process to create source 6365 variable causes the build process to create source
@@ -6374,12 +6377,26 @@
6374 The directory also has the tarballs. 6377 The directory also has the tarballs.
6375 </para></listitem> 6378 </para></listitem>
6376 <listitem><para> 6379 <listitem><para>
6377 <emphasis>Remove Any Git or other SCM Subdirectories From the Downloads Directory:</emphasis> 6380 <emphasis>Optionally Remove Any Git or other SCM Subdirectories From the Downloads Directory:</emphasis>
6378 You can clean up your downloads directory by removing 6381 If you want, you can clean up your downloads directory
6379 any Git or other Source Control Management (SCM) 6382 by removing any Git or other Source Control Management
6380 subdirectories such as 6383 (SCM) subdirectories such as
6381 <filename>${DL_DIR}/git2/*</filename>. 6384 <filename>${DL_DIR}/git2/*</filename>.
6382 </para></listitem> 6385 </para></listitem>
6386 </orderedlist>
6387 </para>
6388
6389 <para>
6390 Once your downloads directory has everything it needs regarding
6391 source files, you can build your target.
6392 Understand that you can use the files to build the target
6393 offline from any machine and at any time.
6394 </para>
6395
6396 <para>
6397 Follow these steps to build your target using the files in the
6398 downloads directory:
6399 <orderedlist>
6383 <listitem><para> 6400 <listitem><para>
6384 <emphasis>Instruct the Build Process to Build Using Local Files:</emphasis> 6401 <emphasis>Instruct the Build Process to Build Using Local Files:</emphasis>
6385 Add the 6402 Add the
@@ -6390,7 +6407,8 @@
6390 </literallayout> 6407 </literallayout>
6391 Using the <filename>BB_NO_NETWORK</filename> 6408 Using the <filename>BB_NO_NETWORK</filename>
6392 variable makes sure that BitBake's fetching process 6409 variable makes sure that BitBake's fetching process
6393 stays local, which means your "own-mirror" is used. 6410 in step 3 stays local, which means files from
6411 your "own-mirror" are used.
6394 </para></listitem> 6412 </para></listitem>
6395 <listitem><para> 6413 <listitem><para>
6396 <emphasis>Start With a Clean Build:</emphasis> 6414 <emphasis>Start With a Clean Build:</emphasis>
@@ -6401,7 +6419,7 @@
6401 </para></listitem> 6419 </para></listitem>
6402 <listitem><para> 6420 <listitem><para>
6403 <emphasis>Build Your Target:</emphasis> 6421 <emphasis>Build Your Target:</emphasis>
6404 Use BitBake to build your target again: 6422 Use BitBake to build your target:
6405 <literallayout class='monospaced'> 6423 <literallayout class='monospaced'>
6406 $ bitbake <replaceable>target</replaceable> 6424 $ bitbake <replaceable>target</replaceable>
6407 </literallayout> 6425 </literallayout>