From 1b877bc9dd3e9048489e6868020876af812cfa5e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 12 Apr 2018 10:57:32 -0700 Subject: documentation: Updated everything for new overview-manual This involved changing the root manual folder from "getting-started" to "overview-manual". Also, every link using the ENTITY "YOCTO_DOCS_GS_URL" was changed to "YOCTO_DOCS_OM_URL". Most manuals had several occurrences of these links. The makefile needed updating to process the new manual and not process the old "getting-started" manual. (From yocto-docs rev: 1abf64e56e9096258038ae37b787a81bf786bb3b) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 28 +++++++++++----------- documentation/dev-manual/dev-manual-newbie.xml | 10 ++++---- documentation/dev-manual/dev-manual-start.xml | 12 +++++----- 3 files changed, 25 insertions(+), 25 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index fd1734beec..85b3a4a8a2 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -24,7 +24,7 @@ each other. For introductory information on the Yocto Project Layer Model, see the - "The Yocto Project Layer Model" + "The Yocto Project Layer Model" section in the Yocto Project Overview and Concepts Manual. @@ -1855,7 +1855,7 @@ You can find more information about the build process in - "The Yocto Project Development Environment" + "The Yocto Project Development Environment" chapter of the Yocto Project Overview and Concepts Manual. @@ -1872,7 +1872,7 @@ Your recipe must have a SRC_URI variable that points to where the source is located. For a graphical representation of source locations, see the - "Sources" + "Sources" section in the Yocto Project Overview and Concepts Manual. @@ -2185,7 +2185,7 @@ containing the current checksum. For more explanation and examples of how to set the LIC_FILES_CHKSUM variable, see the - "Tracking License Changes" + "Tracking License Changes" section in the Yocto Project Overview and Concepts Manual. @@ -2334,7 +2334,7 @@ automatically add a runtime dependency to "mypackage" on "example"). See the - "Automatically Added Runtime Dependencies" + "Automatically Added Runtime Dependencies" section in the Yocto Project Overview and Concepts Manual for further details. @@ -3398,7 +3398,7 @@ The variable LIC_FILES_CHKSUM is used to track source license changes as described in the - "Tracking License Changes" + "Tracking License Changes" section in the Yocto Project Overview and Concepts Manual. You can quickly create Autotool-based recipes in a manner similar to the previous example. @@ -3606,7 +3606,7 @@ allows runtime dependencies between packages to be added automatically. See the - "Automatically Added Runtime Dependencies" + "Automatically Added Runtime Dependencies" section in the Yocto Project Overview and Concepts Manual for more information. @@ -6347,7 +6347,7 @@ can use an existing file provided by the Wic installation. As shipped, kickstart files can be found in the Yocto Project - Source Repositories + Source Repositories in the following two locations: poky/meta-yocto-bsp/wic @@ -8506,7 +8506,7 @@ Some notes from Cal: Because the OpenEmbedded build system uses - "signatures", + "signatures", which are unique to a given build, the build system knows when to rebuild packages. All the inputs into a given task are represented by a @@ -8610,7 +8610,7 @@ Some notes from Cal: For more information on shared state, see the - "Shared State Cache" + "Shared State Cache" section in the Yocto Project Overview and Concepts Manual. @@ -8856,7 +8856,7 @@ Some notes from Cal: connman.inc file in the meta/recipes-connectivity/connman/ directory of the poky - source repository. + source repository. You can also find examples in meta/classes/kernel.bbclass. @@ -10399,7 +10399,7 @@ Some notes from Cal: Enabling build history as previously described causes the OpenEmbedded build system to collect build output information and commit it as a single commit to a local - Git + Git repository. Enabling build history increases your build times slightly, @@ -12261,7 +12261,7 @@ Some notes from Cal: ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1 For tasks that are accelerated through the shared state - (sstate) + (sstate) cache, an additional siginfo file is written into SSTATE_DIR @@ -12370,7 +12370,7 @@ Some notes from Cal: -c, BitBake will only run the task if it considers it "out of date". See the - "Stamp Files and the Rerunning of Tasks" + "Stamp Files and the Rerunning of Tasks" section in the Yocto Project Overview and Concepts Manual for how BitBake determines whether a task is "out of date". diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 1579a4e89e..6ccf21882b 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -99,7 +99,7 @@ with the OpenEmbedded build system is advisable. Of the SCMs BitBake supports, the Yocto Project team strongly recommends using - Git. + Git. Git is a distributed system that is easy to backup, allows you to work remotely, and then connects back to the infrastructure. @@ -311,7 +311,7 @@ Use - Git + Git as the source control system. @@ -325,7 +325,7 @@ Separate the project's Metadata and code by using separate Git repositories. See the - "Yocto Project Source Repositories" + "Yocto Project Source Repositories" section for information on these repositories. See the "Working With Yocto Project Source Files" @@ -549,7 +549,7 @@ pull the change into the component's upstream repository. You do this by pushing to a contribution repository that is upstream. See the - "Git Workflows and the Yocto Project" + "Git Workflows and the Yocto Project" section in the Yocto Project Overview and Concepts Manual for additional concepts on working in the Yocto Project development environment. @@ -749,7 +749,7 @@ Search by File: - Using Git, + Using Git, you can enter the following command to bring up a short list of all commits against a specific file: diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index f7f274bc8d..87d8757a09 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -260,12 +260,12 @@ For concepts and introductory information about Git as it is used in the Yocto Project, see the - "Git" + "Git" section in the Yocto Project Overview and Concepts Manual. For concepts on Yocto Project source repositories, see the - "Yocto Project Source Repositories" + "Yocto Project Source Repositories" section in the Yocto Project Overview and Concepts Manual." @@ -277,7 +277,7 @@ Working from a copy of the upstream Yocto Project - Source Repositories + Source Repositories is the preferred method for obtaining and using a Yocto Project release. You can view the Yocto Project Source Repositories at @@ -306,7 +306,7 @@ Find the URL Used to Clone the Repository: At the bottom of the page, note the URL used to - clone + clone that repository (e.g. &YOCTO_GIT_URL;/poky). @@ -473,7 +473,7 @@ You create your Source Directory by using - Git to clone a local + Git to clone a local copy of the upstream poky repository. Tip The preferred method of getting the Yocto Project Source @@ -748,7 +748,7 @@ Build Directory under tmp/deploy/images. For detailed information on the build process using BitBake, see the - "Images" + "Images" section in the Yocto Project Overview and Concepts Manual. -- cgit v1.2.3-54-g00ecf