From ddc9d240f413c7e48b4861d571054689c5dd860e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 19 Mar 2019 09:06:47 -0600 Subject: dev-manual: Added note about AUTOREV for replicating build Feedback from Paul. (From yocto-docs rev: ea118a9d6fa671de10b9aa8413c7d29951593ec3) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 59 ++++++++++++++++++++-- 1 file changed, 56 insertions(+), 3 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 5f2b6ece3b..5ac8dbf737 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -6370,7 +6370,7 @@ Use BitBake to fetch your sources but inhibit the build: - $ bitbake target --runonly=fetch" + $ bitbake target --runonly=fetch The downloads directory now has a "snapshot" of the source files used for the build. @@ -6382,6 +6382,7 @@ by removing any Git or other Source Control Management (SCM) subdirectories such as ${DL_DIR}/git2/*. + The tarballs already contain these subdirectories. @@ -6398,7 +6399,7 @@ downloads directory: - Instruct the Build Process to Build Using Local Files: + Using Local Files Only: Add the BB_NO_NETWORK variables to your local.conf. @@ -6423,10 +6424,62 @@ $ bitbake target - The build completes using the know local "snapshot" of + The build completes using the known local "snapshot" of source files from your mirror. The resulting tarballs for your "snapshot" of source files are in the downloads directory. + + The offline build does not work if recipes + attempt to find the latest version of software + by setting + SRCREV + to + ${AUTOREV}: + + SRCREV = "${AUTOREV}" + + When a recipe sets + SRCREV to + ${AUTOREV}, the build system + accesses the network in an attempt to determine the + latest version of software from the SCM. + Typically, recipes that use + AUTOREV are custom or + modified recipes. + Recipes that reside in public repositories + usually do not use AUTOREV. + + + If you do have recipes that use + AUTOREV, you can take steps to + still use the recipes in an offline build. + Do the following: + + + Use a configuration generated by + enabling + build history. + + + Use the + buildhistory-collect-srcrevs + command to collect the stored + SRCREV values from + the build's history. + For more information on collecting these + values, see the + "Build History Package Information" + section. + + + Once you have the correct source + revisions, you can modify those recipes + to to set SRCREV + to specific versions of the software. + + + + -- cgit v1.2.3-54-g00ecf