diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2021-03-22 17:10:57 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-03-23 22:54:55 +0000 |
commit | a306baf850a826c89c83e4cfcd4629421c56f73f (patch) | |
tree | e7163f3899e27b005a7a510c80450f38d13e4d7b /documentation/kernel-dev | |
parent | 5de939f61c3d753fa7170e6e71ed31e1fe328d9a (diff) | |
download | poky-a306baf850a826c89c83e4cfcd4629421c56f73f.tar.gz |
Do not assume working from $HOME
In the "Yocto Project Quick Build" instructions
(https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#)
there is an inconsistency that impacts several documents...
People are first instructed to clone the poky git repository, but not
mentioning from which directory. Then, it's consistent to instruct
people to run "cd poky/".
However, later in the instructions, readers are instructed to run "cd
~/poky", which assumes that cloning poky was done from the home
directory. Many other places in the documentation make such an assumption.
This change fixes this, and makes no assumption on where people
have chosen to store their data, in particular where they cloned
the "poky" repository.
This also fixes a few whitespace issues.
(From yocto-docs rev: fd4e365c85df212d7ed70fc1abb3657a4a88b294)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev')
-rw-r--r-- | documentation/kernel-dev/common.rst | 47 |
1 files changed, 23 insertions, 24 deletions
diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst index 58adcc9b70..0e545d1b89 100644 --- a/documentation/kernel-dev/common.rst +++ b/documentation/kernel-dev/common.rst | |||
@@ -57,7 +57,7 @@ section: | |||
57 | the build environment script (i.e. :ref:`structure-core-script`): | 57 | the build environment script (i.e. :ref:`structure-core-script`): |
58 | :: | 58 | :: |
59 | 59 | ||
60 | $ cd ~/poky | 60 | $ cd poky |
61 | $ source oe-init-build-env | 61 | $ source oe-init-build-env |
62 | 62 | ||
63 | .. note:: | 63 | .. note:: |
@@ -74,7 +74,7 @@ section: | |||
74 | ``MACHINE`` variable appropriately in your ``conf/local.conf`` file | 74 | ``MACHINE`` variable appropriately in your ``conf/local.conf`` file |
75 | found in the | 75 | found in the |
76 | :term:`Build Directory` (i.e. | 76 | :term:`Build Directory` (i.e. |
77 | ``~/poky/build`` in this example). | 77 | ``poky/build`` in this example). |
78 | 78 | ||
79 | Also, since you are preparing to work on the kernel image, you need | 79 | Also, since you are preparing to work on the kernel image, you need |
80 | to set the | 80 | to set the |
@@ -94,7 +94,7 @@ section: | |||
94 | ``bitbake-layers create-layer`` command as follows: | 94 | ``bitbake-layers create-layer`` command as follows: |
95 | :: | 95 | :: |
96 | 96 | ||
97 | $ cd ~/poky/build | 97 | $ cd poky/build |
98 | $ bitbake-layers create-layer ../../meta-mylayer | 98 | $ bitbake-layers create-layer ../../meta-mylayer |
99 | NOTE: Starting bitbake server... | 99 | NOTE: Starting bitbake server... |
100 | Add your new layer with 'bitbake-layers add-layer ../../meta-mylayer' | 100 | Add your new layer with 'bitbake-layers add-layer ../../meta-mylayer' |
@@ -119,7 +119,7 @@ section: | |||
119 | ``bblayers.conf`` file as follows: | 119 | ``bblayers.conf`` file as follows: |
120 | :: | 120 | :: |
121 | 121 | ||
122 | $ cd ~/poky/build | 122 | $ cd poky/build |
123 | $ bitbake-layers add-layer ../../meta-mylayer | 123 | $ bitbake-layers add-layer ../../meta-mylayer |
124 | NOTE: Starting bitbake server... | 124 | NOTE: Starting bitbake server... |
125 | $ | 125 | $ |
@@ -128,7 +128,7 @@ section: | |||
128 | specifically for use with images to be run using QEMU: | 128 | specifically for use with images to be run using QEMU: |
129 | :: | 129 | :: |
130 | 130 | ||
131 | $ cd ~/poky/build | 131 | $ cd poky/build |
132 | $ bitbake core-image-minimal -c populate_sdk_ext | 132 | $ bitbake core-image-minimal -c populate_sdk_ext |
133 | 133 | ||
134 | Once | 134 | Once |
@@ -136,21 +136,21 @@ section: | |||
136 | ``*.sh`` file) in the following directory: | 136 | ``*.sh`` file) in the following directory: |
137 | :: | 137 | :: |
138 | 138 | ||
139 | ~/poky/build/tmp/deploy/sdk | 139 | poky/build/tmp/deploy/sdk |
140 | 140 | ||
141 | For this example, the installer file is named | 141 | For this example, the installer file is named |
142 | ``poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-&DISTRO;.sh``. | 142 | ``poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-&DISTRO;.sh``. |
143 | 143 | ||
144 | 6. *Install the Extensible SDK:* Use the following command to install | 144 | 6. *Install the Extensible SDK:* Use the following command to install |
145 | the SDK. For this example, install the SDK in the default | 145 | the SDK. For this example, install the SDK in the default |
146 | ``~/poky_sdk`` directory: | 146 | ``poky_sdk`` directory: |
147 | :: | 147 | :: |
148 | 148 | ||
149 | $ cd ~/poky/build/tmp/deploy/sdk | 149 | $ cd poky/build/tmp/deploy/sdk |
150 | $ ./poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-&DISTRO;.sh | 150 | $ ./poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-&DISTRO;.sh |
151 | Poky (Yocto Project Reference Distro) Extensible SDK installer version &DISTRO; | 151 | Poky (Yocto Project Reference Distro) Extensible SDK installer version &DISTRO; |
152 | ============================================================================ | 152 | ============================================================================ |
153 | Enter target directory for SDK (default: ~/poky_sdk): | 153 | Enter target directory for SDK (default: poky_sdk): |
154 | You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed [Y/n]? Y | 154 | You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed [Y/n]? Y |
155 | Extracting SDK......................................done | 155 | Extracting SDK......................................done |
156 | Setting it up... | 156 | Setting it up... |
@@ -175,7 +175,7 @@ section: | |||
175 | directed by the output from installing the SDK: | 175 | directed by the output from installing the SDK: |
176 | :: | 176 | :: |
177 | 177 | ||
178 | $ source ~/poky_sdk/environment-setup-i586-poky-linux | 178 | $ source poky_sdk/environment-setup-i586-poky-linux |
179 | "SDK environment now set up; additionally you may now run devtool to perform development tasks. | 179 | "SDK environment now set up; additionally you may now run devtool to perform development tasks. |
180 | Run devtool --help for further details. | 180 | Run devtool --help for further details. |
181 | 181 | ||
@@ -240,7 +240,7 @@ section: | |||
240 | section in the Yocto Project Development Tasks Manual. | 240 | section in the Yocto Project Development Tasks Manual. |
241 | :: | 241 | :: |
242 | 242 | ||
243 | $ cd ~/poky | 243 | $ cd poky |
244 | $ git branch | 244 | $ git branch |
245 | master | 245 | master |
246 | * &DISTRO_NAME_NO_CAP; | 246 | * &DISTRO_NAME_NO_CAP; |
@@ -260,7 +260,7 @@ section: | |||
260 | ``MACHINE`` variable appropriately in your ``conf/local.conf`` file | 260 | ``MACHINE`` variable appropriately in your ``conf/local.conf`` file |
261 | found in the | 261 | found in the |
262 | :term:`Build Directory` (i.e. | 262 | :term:`Build Directory` (i.e. |
263 | ``~/poky/build`` in this example). | 263 | ``poky/build`` in this example). |
264 | 264 | ||
265 | Also, since you are preparing to work on the kernel image, you need | 265 | Also, since you are preparing to work on the kernel image, you need |
266 | to set the | 266 | to set the |
@@ -280,7 +280,7 @@ section: | |||
280 | ``bitbake-layers create-layer`` command as follows: | 280 | ``bitbake-layers create-layer`` command as follows: |
281 | :: | 281 | :: |
282 | 282 | ||
283 | $ cd ~/poky/build | 283 | $ cd poky/build |
284 | $ bitbake-layers create-layer ../../meta-mylayer | 284 | $ bitbake-layers create-layer ../../meta-mylayer |
285 | NOTE: Starting bitbake server... | 285 | NOTE: Starting bitbake server... |
286 | Add your new layer with 'bitbake-layers add-layer ../../meta-mylayer' | 286 | Add your new layer with 'bitbake-layers add-layer ../../meta-mylayer' |
@@ -304,7 +304,7 @@ section: | |||
304 | ``bblayers.conf`` file as follows: | 304 | ``bblayers.conf`` file as follows: |
305 | :: | 305 | :: |
306 | 306 | ||
307 | $ cd ~/poky/build | 307 | $ cd poky/build |
308 | $ bitbake-layers add-layer ../../meta-mylayer | 308 | $ bitbake-layers add-layer ../../meta-mylayer |
309 | NOTE: Starting bitbake server ... | 309 | NOTE: Starting bitbake server ... |
310 | $ | 310 | $ |
@@ -398,7 +398,6 @@ home directory: | |||
398 | 1. *Create Structure*: Create the layer's structure: | 398 | 1. *Create Structure*: Create the layer's structure: |
399 | :: | 399 | :: |
400 | 400 | ||
401 | $ cd $HOME | ||
402 | $ mkdir meta-mylayer | 401 | $ mkdir meta-mylayer |
403 | $ mkdir meta-mylayer/conf | 402 | $ mkdir meta-mylayer/conf |
404 | $ mkdir meta-mylayer/recipes-kernel | 403 | $ mkdir meta-mylayer/recipes-kernel |
@@ -819,12 +818,12 @@ the ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" Se | |||
819 | 818 | ||
820 | 1. *Change the working directory*: In the previous step, the output | 819 | 1. *Change the working directory*: In the previous step, the output |
821 | noted where you can find the source files (e.g. | 820 | noted where you can find the source files (e.g. |
822 | ``~/poky_sdk/workspace/sources/linux-yocto``). Change to where the | 821 | ``poky_sdk/workspace/sources/linux-yocto``). Change to where the |
823 | kernel source code is before making your edits to the | 822 | kernel source code is before making your edits to the |
824 | ``calibrate.c`` file: | 823 | ``calibrate.c`` file: |
825 | :: | 824 | :: |
826 | 825 | ||
827 | $ cd ~/poky_sdk/workspace/sources/linux-yocto | 826 | $ cd poky_sdk/workspace/sources/linux-yocto |
828 | 827 | ||
829 | 2. *Edit the source file*: Edit the ``init/calibrate.c`` file to have | 828 | 2. *Edit the source file*: Edit the ``init/calibrate.c`` file to have |
830 | the following changes: | 829 | the following changes: |
@@ -896,7 +895,7 @@ the ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" Se | |||
896 | and use these Git commands to stage and commit your changes: | 895 | and use these Git commands to stage and commit your changes: |
897 | :: | 896 | :: |
898 | 897 | ||
899 | $ cd ~/poky_sdk/workspace/sources/linux-yocto | 898 | $ cd poky_sdk/workspace/sources/linux-yocto |
900 | $ git status | 899 | $ git status |
901 | $ git add init/calibrate.c | 900 | $ git add init/calibrate.c |
902 | $ git commit -m "calibrate: Add printk example" | 901 | $ git commit -m "calibrate: Add printk example" |
@@ -926,7 +925,7 @@ the ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" Se | |||
926 | set up to run BitBake: | 925 | set up to run BitBake: |
927 | :: | 926 | :: |
928 | 927 | ||
929 | $ cd ~/poky/build | 928 | $ cd poky/build |
930 | $ bitbake core-image-minimal | 929 | $ bitbake core-image-minimal |
931 | 930 | ||
932 | Using Traditional Kernel Development to Patch the Kernel | 931 | Using Traditional Kernel Development to Patch the Kernel |
@@ -1015,7 +1014,7 @@ Section. | |||
1015 | to the following to your ``local.conf``: | 1014 | to the following to your ``local.conf``: |
1016 | :: | 1015 | :: |
1017 | 1016 | ||
1018 | $ cd ~/poky/build/conf | 1017 | $ cd poky/build/conf |
1019 | 1018 | ||
1020 | Add the following to the ``local.conf``: | 1019 | Add the following to the ``local.conf``: |
1021 | :: | 1020 | :: |
@@ -1037,7 +1036,7 @@ Section. | |||
1037 | you can now use BitBake to build the image: | 1036 | you can now use BitBake to build the image: |
1038 | :: | 1037 | :: |
1039 | 1038 | ||
1040 | $ cd ~/poky/build | 1039 | $ cd poky/build |
1041 | $ bitbake core-image-minimal | 1040 | $ bitbake core-image-minimal |
1042 | 1041 | ||
1043 | 5. *Boot the image*: Boot the modified image in the QEMU emulator using | 1042 | 5. *Boot the image*: Boot the modified image in the QEMU emulator using |
@@ -1045,7 +1044,7 @@ Section. | |||
1045 | with no password: | 1044 | with no password: |
1046 | :: | 1045 | :: |
1047 | 1046 | ||
1048 | $ cd ~/poky/build | 1047 | $ cd poky/build |
1049 | $ runqemu qemux86 | 1048 | $ runqemu qemux86 |
1050 | 1049 | ||
1051 | 6. *Look for Your Changes:* As QEMU booted, you might have seen your | 1050 | 6. *Look for Your Changes:* As QEMU booted, you might have seen your |
@@ -1119,7 +1118,7 @@ Section. | |||
1119 | the following sequence of commands: | 1118 | the following sequence of commands: |
1120 | :: | 1119 | :: |
1121 | 1120 | ||
1122 | $ cd ~/poky/build | 1121 | $ cd poky/build |
1123 | $ bitbake -c cleanall yocto-linux | 1122 | $ bitbake -c cleanall yocto-linux |
1124 | $ bitbake core-image-minimal -c cleanall | 1123 | $ bitbake core-image-minimal -c cleanall |
1125 | $ bitbake core-image-minimal | 1124 | $ bitbake core-image-minimal |
@@ -1172,7 +1171,7 @@ environment, you must do the following: | |||
1172 | The following commands initialize the BitBake environment, run the | 1171 | The following commands initialize the BitBake environment, run the |
1173 | :ref:`ref-tasks-kernel_configme` | 1172 | :ref:`ref-tasks-kernel_configme` |
1174 | task, and launch ``menuconfig``. These commands assume the Source | 1173 | task, and launch ``menuconfig``. These commands assume the Source |
1175 | Directory's top-level folder is ``~/poky``: | 1174 | Directory's top-level folder is ``poky``: |
1176 | :: | 1175 | :: |
1177 | 1176 | ||
1178 | $ cd poky | 1177 | $ cd poky |