summaryrefslogtreecommitdiffstats
path: root/documentation/what-i-wish-id-known.rst
diff options
context:
space:
mode:
authorQuentin Schulz <foss@0leil.net>2020-09-17 01:58:59 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-09-17 10:09:36 +0100
commitc387f0c2543a9dd7f8eca069629ede4bb5ec5dba (patch)
treed0a7fccf9b84915862b1174ae75cd0437a60bb2d /documentation/what-i-wish-id-known.rst
parent6813141743f4263e6b03fd7294f9cec4ec1a3194 (diff)
downloadpoky-c387f0c2543a9dd7f8eca069629ede4bb5ec5dba.tar.gz
sphinx: replace special quotes with single and double quotes
(From yocto-docs rev: 0aeb7a94abcef3cb3850c753dd0a243f381e6675) Signed-off-by: Quentin Schulz <foss@0leil.net> Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/what-i-wish-id-known.rst')
-rw-r--r--documentation/what-i-wish-id-known.rst18
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/what-i-wish-id-known.rst b/documentation/what-i-wish-id-known.rst
index cf378747c6..67bf84e07f 100644
--- a/documentation/what-i-wish-id-known.rst
+++ b/documentation/what-i-wish-id-known.rst
@@ -8,7 +8,7 @@ What I wish I'd known about Yocto Project
8 8
9.. note:: 9.. note::
10 10
11 Before reading further, make sure youve taken a look at the 11 Before reading further, make sure you've taken a look at the
12 :yocto_home:`Software Overview</software-overview>` page which presents the 12 :yocto_home:`Software Overview</software-overview>` page which presents the
13 definitions for many of the terms referenced here. Also, know that some of the 13 definitions for many of the terms referenced here. Also, know that some of the
14 information here won't make sense now, but as you start developing, it is the 14 information here won't make sense now, but as you start developing, it is the
@@ -16,8 +16,8 @@ What I wish I'd known about Yocto Project
16 working with Yocto Project and they are updated regularly. 16 working with Yocto Project and they are updated regularly.
17 17
18Using the Yocto Project is fairly easy, *until something goes wrong*. Without an 18Using the Yocto Project is fairly easy, *until something goes wrong*. Without an
19understanding of how the build process works, youll find yourself trying to 19understanding of how the build process works, you'll find yourself trying to
20troubleshoot a black box. Here are a few items that new users wished they had 20troubleshoot "a black box". Here are a few items that new users wished they had
21known before embarking on their first build with Yocto Project. Feel free to 21known before embarking on their first build with Yocto Project. Feel free to
22contact us with other suggestions. 22contact us with other suggestions.
23 23
@@ -34,7 +34,7 @@ contact us with other suggestions.
34 </software-over/layer/>`. Generally check the Compatible layer index first, 34 </software-over/layer/>`. Generally check the Compatible layer index first,
35 and if you don't find the necessary layer check the general layer index. The 35 and if you don't find the necessary layer check the general layer index. The
36 layer index is an original artifact from the Open Embedded Project. As such, 36 layer index is an original artifact from the Open Embedded Project. As such,
37 that index doesnt have the curating and testing that the Yocto Project 37 that index doesn't have the curating and testing that the Yocto Project
38 provides on Yocto Project Compatible layer list, but the latter has fewer 38 provides on Yocto Project Compatible layer list, but the latter has fewer
39 entries. Know that when you start searching in the layer index that not all 39 entries. Know that when you start searching in the layer index that not all
40 layers have the same level of maturity, validation, or usability. Nor do 40 layers have the same level of maturity, validation, or usability. Nor do
@@ -110,7 +110,7 @@ contact us with other suggestions.
110 :ref:`bitbake-user-manual/bitbake-user-manual-intro:generating dependency 110 :ref:`bitbake-user-manual/bitbake-user-manual-intro:generating dependency
111 graphs` section in the BitBake User Manual. 111 graphs` section in the BitBake User Manual.
112 112
113#. **Heres how you decode magic folder names in tmp/work:** 113#. **Here's how you decode "magic" folder names in tmp/work:**
114 The build system fetches, unpacks, preprocesses, and builds. If something 114 The build system fetches, unpacks, preprocesses, and builds. If something
115 goes wrong, the build system reports to you directly the path to a folder 115 goes wrong, the build system reports to you directly the path to a folder
116 where the temporary (build/tmp) files and packages reside resulting from the 116 where the temporary (build/tmp) files and packages reside resulting from the
@@ -128,8 +128,8 @@ contact us with other suggestions.
128 Yocto Project, the instructions found in the 128 Yocto Project, the instructions found in the
129 :doc:`brief-yoctoprojectqs/brief-yoctoprojectqs` show how to create an image 129 :doc:`brief-yoctoprojectqs/brief-yoctoprojectqs` show how to create an image
130 and then run or flash that image. However, you can actually build just a 130 and then run or flash that image. However, you can actually build just a
131 single recipe. Thus, if some dependency or recipe isnt working, you can just 131 single recipe. Thus, if some dependency or recipe isn't working, you can just
132 say bitbake foo where "foo" is the name for a specific recipe. As you 132 say "bitbake foo" where "foo" is the name for a specific recipe. As you
133 become more advanced using the Yocto Project, and if builds are failing, it 133 become more advanced using the Yocto Project, and if builds are failing, it
134 can be useful to make sure the fetch itself works as desired. Here are some 134 can be useful to make sure the fetch itself works as desired. Here are some
135 valuable links: :ref:`dev-manual/dev-manual-common-tasks:Using a Development 135 valuable links: :ref:`dev-manual/dev-manual-common-tasks:Using a Development
@@ -147,11 +147,11 @@ contact us with other suggestions.
147 the recipe is building but are different parts (packages) of the build 147 the recipe is building but are different parts (packages) of the build
148 (i.e. the main package, the doc package, the debug symbols package, the 148 (i.e. the main package, the doc package, the debug symbols package, the
149 separate utilities package, and so forth). The build system splits out the 149 separate utilities package, and so forth). The build system splits out the
150 packages so that you dont need to install the packages you dont want or 150 packages so that you don't need to install the packages you don't want or
151 need, which is advantageous because you are building for small devices when 151 need, which is advantageous because you are building for small devices when
152 developing for embedded and IoT. 152 developing for embedded and IoT.
153 153
154#. **You will want to learn about and know whats packaged in rootfs.** 154#. **You will want to learn about and know what's packaged in rootfs.**
155 155
156#. **Create your own image recipe:** 156#. **Create your own image recipe:**
157 There are a number of ways to create your own image recipe. We suggest you 157 There are a number of ways to create your own image recipe. We suggest you