summaryrefslogtreecommitdiffstats
path: root/documentation/what-i-wish-id-known.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/what-i-wish-id-known.rst')
-rw-r--r--documentation/what-i-wish-id-known.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/what-i-wish-id-known.rst b/documentation/what-i-wish-id-known.rst
index 5bc55804f6..ddee6ad749 100644
--- a/documentation/what-i-wish-id-known.rst
+++ b/documentation/what-i-wish-id-known.rst
@@ -49,7 +49,7 @@ contact us with other suggestions.
49 their silicon. These layers have names such as "meta-intel" or "meta-ti". Try 49 their silicon. These layers have names such as "meta-intel" or "meta-ti". Try
50 not to build layers from scratch. If you do have custom silicon, use one of 50 not to build layers from scratch. If you do have custom silicon, use one of
51 these layers as a guide or template and familiarize yourself with the 51 these layers as a guide or template and familiarize yourself with the
52 :doc:`bsp-guide/index`. 52 :doc:`/bsp-guide/index`.
53 53
54#. **Do not put everything into one layer:** 54#. **Do not put everything into one layer:**
55 Use different layers to logically separate information in your build. As an 55 Use different layers to logically separate information in your build. As an
@@ -127,7 +127,7 @@ contact us with other suggestions.
127 You can build and run a specific task for a specific package (including 127 You can build and run a specific task for a specific package (including
128 devshell) or even a single recipe. When developers first start using the 128 devshell) or even a single recipe. When developers first start using the
129 Yocto Project, the instructions found in the 129 Yocto Project, the instructions found in the
130 :doc:`brief-yoctoprojectqs/index` show how to create an image 130 :doc:`/brief-yoctoprojectqs/index` show how to create an image
131 and then run or flash that image. However, you can actually build just a 131 and then run or flash that image. However, you can actually build just a
132 single recipe. Thus, if some dependency or recipe isn't working, you can just 132 single recipe. Thus, if some dependency or recipe isn't working, you can just
133 say "bitbake foo" where "foo" is the name for a specific recipe. As you 133 say "bitbake foo" where "foo" is the name for a specific recipe. As you
@@ -136,7 +136,7 @@ contact us with other suggestions.
136 valuable links: :ref:`dev-manual/development-shell:Using a Development 136 valuable links: :ref:`dev-manual/development-shell:Using a Development
137 Shell` for information on how to build and run a specific task using 137 Shell` for information on how to build and run a specific task using
138 devshell. Also, the :ref:`SDK manual shows how to build out a specific recipe 138 devshell. Also, the :ref:`SDK manual shows how to build out a specific recipe
139 <sdk-manual/extensible:use \`\`devtool modify\`\` to modify the source of an existing component>`. 139 <dev-manual/devtool:use \`\`devtool modify\`\` to modify the source of an existing component>`.
140 140
141#. **An ambiguous definition: Package vs Recipe:** 141#. **An ambiguous definition: Package vs Recipe:**
142 A recipe contains instructions the build system uses to create 142 A recipe contains instructions the build system uses to create