blob: 6816ce58465d62f5a3bdd4740c48fe89a96c9a77 [file] [log] [blame]
Andrew Geisslerf0343792020-11-18 10:42:21 -06001.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
Andrew Geisslerc9f78652020-09-18 14:11:35 -05002
3***********************************
4Setting Up to Use the Yocto Project
5***********************************
6
7This chapter provides guidance on how to prepare to use the Yocto
8Project. You can learn about creating a team environment to develop
9using the Yocto Project, how to set up a :ref:`build
Andrew Geissler09209ee2020-12-13 08:44:15 -060010host <dev-manual/start:preparing the build host>`, how to locate
Andrew Geisslerc9f78652020-09-18 14:11:35 -050011Yocto Project source repositories, and how to create local Git
12repositories.
13
Andrew Geisslerc9f78652020-09-18 14:11:35 -050014Creating a Team Development Environment
15=======================================
16
17It might not be immediately clear how you can use the Yocto Project in a
18team development environment, or how to scale it for a large team of
19developers. You can adapt the Yocto Project to many different use cases
20and scenarios; however, this flexibility could cause difficulties if you
21are trying to create a working setup that scales effectively.
22
23To help you understand how to set up this type of environment, this
24section presents a procedure that gives you information that can help
25you get the results you want. The procedure is high-level and presents
26some of the project's most successful experiences, practices, solutions,
27and available technologies that have proved to work well in the past;
28however, keep in mind, the procedure here is simply a starting point.
29You can build off these steps and customize the procedure to fit any
30particular working environment and set of practices.
31
321. *Determine Who is Going to be Developing:* You first need to
33 understand who is going to be doing anything related to the Yocto
34 Project and determine their roles. Making this determination is
35 essential to completing subsequent steps, which are to get your
36 equipment together and set up your development environment's
37 hardware topology.
38
William A. Kennington IIIac69b482021-06-02 12:28:27 -070039 Here are possible roles:
Andrew Geisslerc9f78652020-09-18 14:11:35 -050040
41 - *Application Developer:* This type of developer does application
42 level work on top of an existing software stack.
43
44 - *Core System Developer:* This type of developer works on the
45 contents of the operating system image itself.
46
47 - *Build Engineer:* This type of developer manages Autobuilders and
48 releases. Depending on the specifics of the environment, not all
49 situations might need a Build Engineer.
50
51 - *Test Engineer:* This type of developer creates and manages
52 automated tests that are used to ensure all application and core
53 system development meets desired quality standards.
54
552. *Gather the Hardware:* Based on the size and make-up of the team,
56 get the hardware together. Ideally, any development, build, or test
57 engineer uses a system that runs a supported Linux distribution.
58 These systems, in general, should be high performance (e.g. dual,
59 six-core Xeons with 24 Gbytes of RAM and plenty of disk space). You
60 can help ensure efficiency by having any machines used for testing
61 or that run Autobuilders be as high performance as possible.
62
63 .. note::
64
65 Given sufficient processing power, you might also consider
66 building Yocto Project development containers to be run under
67 Docker, which is described later.
68
693. *Understand the Hardware Topology of the Environment:* Once you
70 understand the hardware involved and the make-up of the team, you
71 can understand the hardware topology of the development environment.
72 You can get a visual idea of the machines and their roles across the
73 development environment.
74
754. *Use Git as Your Source Control Manager (SCM):* Keeping your
76 :term:`Metadata` (i.e. recipes,
77 configuration files, classes, and so forth) and any software you are
78 developing under the control of an SCM system that is compatible
79 with the OpenEmbedded build system is advisable. Of all of the SCMs
80 supported by BitBake, the Yocto Project team strongly recommends using
Andrew Geissler09209ee2020-12-13 08:44:15 -060081 :ref:`overview-manual/development-environment:git`.
Andrew Geisslerc9f78652020-09-18 14:11:35 -050082 Git is a distributed system
83 that is easy to back up, allows you to work remotely, and then
84 connects back to the infrastructure.
85
86 .. note::
87
88 For information about BitBake, see the
Andrew Geissler4c19ea12020-10-27 13:52:24 -050089 :doc:`bitbake:index`.
Andrew Geisslerc9f78652020-09-18 14:11:35 -050090
91 It is relatively easy to set up Git services and create
Andrew Geissler4c19ea12020-10-27 13:52:24 -050092 infrastructure like :yocto_git:`/`, which is based on
Andrew Geisslerc9f78652020-09-18 14:11:35 -050093 server software called ``gitolite`` with ``cgit`` being used to
94 generate the web interface that lets you view the repositories. The
95 ``gitolite`` software identifies users using SSH keys and allows
96 branch-based access controls to repositories that you can control as
97 little or as much as necessary.
98
99 .. note::
100
101 The setup of these services is beyond the scope of this manual.
William A. Kennington IIIac69b482021-06-02 12:28:27 -0700102 However, here are sites describing how to perform setup:
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500103
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500104 - `Gitolite <https://gitolite.com>`__: Information for
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500105 ``gitolite``.
106
107 - `Interfaces, frontends, and
108 tools <https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools>`__:
109 Documentation on how to create interfaces and frontends for
110 Git.
111
1125. *Set up the Application Development Machines:* As mentioned earlier,
113 application developers are creating applications on top of existing
114 software stacks. Following are some best practices for setting up
115 machines used for application development:
116
117 - Use a pre-built toolchain that contains the software stack
118 itself. Then, develop the application code on top of the stack.
119 This method works well for small numbers of relatively isolated
120 applications.
121
122 - Keep your cross-development toolchains updated. You can do this
123 through provisioning either as new toolchain downloads or as
124 updates through a package update mechanism using ``opkg`` to
125 provide updates to an existing toolchain. The exact mechanics of
126 how and when to do this depend on local policy.
127
128 - Use multiple toolchains installed locally into different
129 locations to allow development across versions.
130
1316. *Set up the Core Development Machines:* As mentioned earlier, core
132 developers work on the contents of the operating system itself.
133 Following are some best practices for setting up machines used for
134 developing images:
135
136 - Have the :term:`OpenEmbedded Build System` available on
137 the developer workstations so developers can run their own builds
138 and directly rebuild the software stack.
139
140 - Keep the core system unchanged as much as possible and do your
141 work in layers on top of the core system. Doing so gives you a
142 greater level of portability when upgrading to new versions of
143 the core system or Board Support Packages (BSPs).
144
145 - Share layers amongst the developers of a particular project and
146 contain the policy configuration that defines the project.
147
1487. *Set up an Autobuilder:* Autobuilders are often the core of the
149 development environment. It is here that changes from individual
150 developers are brought together and centrally tested. Based on this
151 automated build and test environment, subsequent decisions about
152 releases can be made. Autobuilders also allow for "continuous
153 integration" style testing of software components and regression
154 identification and tracking.
155
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500156 See ":yocto_ab:`Yocto Project Autobuilder <>`" for more
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500157 information and links to buildbot. The Yocto Project team has found
158 this implementation works well in this role. A public example of
159 this is the Yocto Project Autobuilders, which the Yocto Project team
160 uses to test the overall health of the project.
161
162 The features of this system are:
163
164 - Highlights when commits break the build.
165
166 - Populates an :ref:`sstate
Andrew Geissler09209ee2020-12-13 08:44:15 -0600167 cache <overview-manual/concepts:shared state cache>` from which
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500168 developers can pull rather than requiring local builds.
169
170 - Allows commit hook triggers, which trigger builds when commits
171 are made.
172
173 - Allows triggering of automated image booting and testing under
174 the QuickEMUlator (QEMU).
175
176 - Supports incremental build testing and from-scratch builds.
177
178 - Shares output that allows developer testing and historical
179 regression investigation.
180
181 - Creates output that can be used for releases.
182
183 - Allows scheduling of builds so that resources can be used
184 efficiently.
185
1868. *Set up Test Machines:* Use a small number of shared, high
187 performance systems for testing purposes. Developers can use these
188 systems for wider, more extensive testing while they continue to
189 develop locally using their primary development system.
190
1919. *Document Policies and Change Flow:* The Yocto Project uses a
William A. Kennington IIIac69b482021-06-02 12:28:27 -0700192 hierarchical structure and a pull model. There are scripts to create and
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500193 send pull requests (i.e. ``create-pull-request`` and
194 ``send-pull-request``). This model is in line with other open source
195 projects where maintainers are responsible for specific areas of the
196 project and a single maintainer handles the final "top-of-tree"
197 merges.
198
199 .. note::
200
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500201 You can also use a more collective push model. The ``gitolite``
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500202 software supports both the push and pull models quite easily.
203
204 As with any development environment, it is important to document the
205 policy used as well as any main project guidelines so they are
206 understood by everyone. It is also a good idea to have
207 well-structured commit messages, which are usually a part of a
208 project's guidelines. Good commit messages are essential when
209 looking back in time and trying to understand why changes were made.
210
211 If you discover that changes are needed to the core layer of the
212 project, it is worth sharing those with the community as soon as
213 possible. Chances are if you have discovered the need for changes,
214 someone else in the community needs them also.
215
21610. *Development Environment Summary:* Aside from the previous steps,
William A. Kennington IIIac69b482021-06-02 12:28:27 -0700217 here are best practices within the Yocto Project development
218 environment:
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500219
Andrew Geissler09209ee2020-12-13 08:44:15 -0600220 - Use :ref:`overview-manual/development-environment:git` as the source control
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500221 system.
222
223 - Maintain your Metadata in layers that make sense for your
Andrew Geissler09209ee2020-12-13 08:44:15 -0600224 situation. See the ":ref:`overview-manual/yp-intro:the yocto project layer model`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500225 section in the Yocto Project Overview and Concepts Manual and the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600226 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500227 section for more information on layers.
228
229 - Separate the project's Metadata and code by using separate Git
Andrew Geissler09209ee2020-12-13 08:44:15 -0600230 repositories. See the ":ref:`overview-manual/development-environment:yocto project source repositories`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500231 section in the Yocto Project Overview and Concepts Manual for
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500232 information on these repositories. See the
233 ":ref:`dev-manual/start:locating yocto project source files`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500234 section for information on how to set up local Git repositories
235 for related upstream Yocto Project Git repositories.
236
237 - Set up the directory for the shared state cache
238 (:term:`SSTATE_DIR`) where
239 it makes sense. For example, set up the sstate cache on a system
240 used by developers in the same organization and share the same
241 source directories on their machines.
242
243 - Set up an Autobuilder and have it populate the sstate cache and
244 source directories.
245
246 - The Yocto Project community encourages you to send patches to the
247 project to fix bugs or add features. If you do submit patches,
248 follow the project commit guidelines for writing good commit
249 messages. See the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600250 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500251 section.
252
253 - Send changes to the core sooner than later as others are likely
254 to run into the same issues. For some guidance on mailing lists
255 to use, see the list in the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600256 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500257 section. For a description
258 of the available mailing lists, see the ":ref:`resources-mailinglist`" section in
259 the Yocto Project Reference Manual.
260
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500261Preparing the Build Host
262========================
263
264This section provides procedures to set up a system to be used as your
265:term:`Build Host` for
266development using the Yocto Project. Your build host can be a native
267Linux machine (recommended), it can be a machine (Linux, Mac, or
268Windows) that uses `CROPS <https://github.com/crops/poky-container>`__,
269which leverages `Docker Containers <https://www.docker.com/>`__ or it
270can be a Windows machine capable of running Windows Subsystem For Linux
271v2 (WSL).
272
273.. note::
274
275 The Yocto Project is not compatible with
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500276 `Windows Subsystem for Linux v1 <https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux>`__.
277 It is compatible but not officially supported nor validated with
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500278 WSLv2. If you still decide to use WSL please upgrade to
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500279 `WSLv2 <https://docs.microsoft.com/en-us/windows/wsl/install-win10>`__.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500280
281Once your build host is set up to use the Yocto Project, further steps
282are necessary depending on what you want to accomplish. See the
283following references for information on how to prepare for Board Support
284Package (BSP) development and kernel development:
285
286- *BSP Development:* See the ":ref:`bsp-guide/bsp:preparing your build host to work with bsp layers`"
287 section in the Yocto Project Board Support Package (BSP) Developer's
288 Guide.
289
Andrew Geissler09209ee2020-12-13 08:44:15 -0600290- *Kernel Development:* See the ":ref:`kernel-dev/common:preparing the build host to work on the kernel`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500291 section in the Yocto Project Linux Kernel Development Manual.
292
293Setting Up a Native Linux Host
294------------------------------
295
296Follow these steps to prepare a native Linux machine as your Yocto
297Project Build Host:
298
2991. *Use a Supported Linux Distribution:* You should have a reasonably
300 current Linux-based host system. You will have the best results with
301 a recent release of Fedora, openSUSE, Debian, Ubuntu, RHEL or CentOS
302 as these releases are frequently tested against the Yocto Project and
303 officially supported. For a list of the distributions under
304 validation and their status, see the ":ref:`Supported Linux
305 Distributions <detailed-supported-distros>`"
306 section in the Yocto Project Reference Manual and the wiki page at
Andrew Geissler09209ee2020-12-13 08:44:15 -0600307 :yocto_wiki:`Distribution Support </Distribution_Support>`.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500308
3092. *Have Enough Free Memory:* Your system should have at least 50 Gbytes
310 of free disk space for building images.
311
3123. *Meet Minimal Version Requirements:* The OpenEmbedded build system
313 should be able to run on any modern distribution that has the
Andrew Geissler615f2f12022-07-15 14:00:58 -0500314 following versions for Git, tar, Python, gcc and make.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500315
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500316 - Git &MIN_GIT_VERSION; or greater
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500317
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500318 - tar &MIN_TAR_VERSION; or greater
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500319
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500320 - Python &MIN_PYTHON_VERSION; or greater.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500321
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500322 - gcc &MIN_GCC_VERSION; or greater.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500323
Andrew Geissler615f2f12022-07-15 14:00:58 -0500324 - GNU make &MIN_MAKE_VERSION; or greater
325
Andrew Geissler5199d832021-09-24 16:47:35 -0500326 If your build host does not meet any of these listed version
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500327 requirements, you can take steps to prepare the system so that you
328 can still use the Yocto Project. See the
Andrew Geissler615f2f12022-07-15 14:00:58 -0500329 ":ref:`ref-manual/system-requirements:required git, tar, python, make and gcc versions`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500330 section in the Yocto Project Reference Manual for information.
331
3324. *Install Development Host Packages:* Required development host
333 packages vary depending on your build host and what you want to do
334 with the Yocto Project. Collectively, the number of required packages
335 is large if you want to be able to cover all cases.
336
337 For lists of required packages for all scenarios, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600338 ":ref:`ref-manual/system-requirements:required packages for the build host`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500339 section in the Yocto Project Reference Manual.
340
341Once you have completed the previous steps, you are ready to continue
342using a given development path on your native Linux machine. If you are
343going to use BitBake, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600344":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500345section. If you are going
Andrew Geissler09209ee2020-12-13 08:44:15 -0600346to use the Extensible SDK, see the ":doc:`/sdk-manual/extensible`" Chapter in the Yocto
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500347Project Application Development and the Extensible Software Development
Andrew Geissler09209ee2020-12-13 08:44:15 -0600348Kit (eSDK) manual. If you want to work on the kernel, see the :doc:`/kernel-dev/index`. If you are going to use
349Toaster, see the ":doc:`/toaster-manual/setup-and-use`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500350section in the Toaster User Manual.
351
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500352Setting Up to Use CROss PlatformS (CROPS)
353-----------------------------------------
354
355With `CROPS <https://github.com/crops/poky-container>`__, which
356leverages `Docker Containers <https://www.docker.com/>`__, you can
357create a Yocto Project development environment that is operating system
358agnostic. You can set up a container in which you can develop using the
359Yocto Project on a Windows, Mac, or Linux machine.
360
361Follow these general steps to prepare a Windows, Mac, or Linux machine
362as your Yocto Project build host:
363
3641. *Determine What Your Build Host Needs:*
365 `Docker <https://www.docker.com/what-docker>`__ is a software
366 container platform that you need to install on the build host.
367 Depending on your build host, you might have to install different
368 software to support Docker containers. Go to the Docker installation
369 page and read about the platform requirements in "`Supported
Andrew Geisslerc3d88e42020-10-02 09:45:00 -0500370 Platforms <https://docs.docker.com/engine/install/#supported-platforms>`__"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500371 your build host needs to run containers.
372
3732. *Choose What To Install:* Depending on whether or not your build host
374 meets system requirements, you need to install "Docker CE Stable" or
375 the "Docker Toolbox". Most situations call for Docker CE. However, if
376 you have a build host that does not meet requirements (e.g.
377 Pre-Windows 10 or Windows 10 "Home" version), you must install Docker
378 Toolbox instead.
379
3803. *Go to the Install Site for Your Platform:* Click the link for the
381 Docker edition associated with your build host's native software. For
382 example, if your build host is running Microsoft Windows Version 10
383 and you want the Docker CE Stable edition, click that link under
384 "Supported Platforms".
385
3864. *Install the Software:* Once you have understood all the
387 pre-requisites, you can download and install the appropriate
388 software. Follow the instructions for your specific machine and the
389 type of the software you need to install:
390
Andrew Geisslerc926e172021-05-07 16:11:35 -0500391 - Install `Docker Desktop on
Andrew Geisslerc3d88e42020-10-02 09:45:00 -0500392 Windows <https://docs.docker.com/docker-for-windows/install/#install-docker-desktop-on-windows>`__
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500393 for Windows build hosts that meet requirements.
394
Andrew Geisslerc926e172021-05-07 16:11:35 -0500395 - Install `Docker Desktop on
Andrew Geisslerc3d88e42020-10-02 09:45:00 -0500396 MacOs <https://docs.docker.com/docker-for-mac/install/#install-and-run-docker-desktop-on-mac>`__
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500397 for Mac build hosts that meet requirements.
398
Andrew Geisslerc926e172021-05-07 16:11:35 -0500399 - Install `Docker Engine on
400 CentOS <https://docs.docker.com/engine/install/centos/>`__
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500401 for Linux build hosts running the CentOS distribution.
402
Andrew Geisslerc926e172021-05-07 16:11:35 -0500403 - Install `Docker Engine on
404 Debian <https://docs.docker.com/engine/install/debian/>`__
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500405 for Linux build hosts running the Debian distribution.
406
Andrew Geisslerc926e172021-05-07 16:11:35 -0500407 - Install `Docker Engine for
408 Fedora <https://docs.docker.com/engine/install/fedora/>`__
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500409 for Linux build hosts running the Fedora distribution.
410
Andrew Geisslerc926e172021-05-07 16:11:35 -0500411 - Install `Docker Engine for
412 Ubuntu <https://docs.docker.com/engine/install/ubuntu/>`__
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500413 for Linux build hosts running the Ubuntu distribution.
414
4155. *Optionally Orient Yourself With Docker:* If you are unfamiliar with
416 Docker and the container concept, you can learn more here -
417 https://docs.docker.com/get-started/.
418
4196. *Launch Docker or Docker Toolbox:* You should be able to launch
420 Docker or the Docker Toolbox and have a terminal shell on your
421 development host.
422
4237. *Set Up the Containers to Use the Yocto Project:* Go to
424 https://github.com/crops/docker-win-mac-docs/wiki and follow
425 the directions for your particular build host (i.e. Linux, Mac, or
426 Windows).
427
428 Once you complete the setup instructions for your machine, you have
429 the Poky, Extensible SDK, and Toaster containers available. You can
430 click those links from the page and learn more about using each of
431 those containers.
432
433Once you have a container set up, everything is in place to develop just
434as if you were running on a native Linux machine. If you are going to
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500435use the Poky container, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600436":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500437section. If you are going to use the Extensible SDK container, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600438":doc:`/sdk-manual/extensible`" Chapter in the Yocto
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500439Project Application Development and the Extensible Software Development
440Kit (eSDK) manual. If you are going to use the Toaster container, see
Andrew Geissler09209ee2020-12-13 08:44:15 -0600441the ":doc:`/toaster-manual/setup-and-use`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500442section in the Toaster User Manual.
443
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500444Setting Up to Use Windows Subsystem For Linux (WSLv2)
445-----------------------------------------------------
446
447With `Windows Subsystem for Linux
448(WSLv2) <https://docs.microsoft.com/en-us/windows/wsl/wsl2-about>`__,
449you can create a Yocto Project development environment that allows you
450to build on Windows. You can set up a Linux distribution inside Windows
451in which you can develop using the Yocto Project.
452
453Follow these general steps to prepare a Windows machine using WSLv2 as
454your Yocto Project build host:
455
4561. *Make sure your Windows 10 machine is capable of running WSLv2:*
457 WSLv2 is only available for Windows 10 builds > 18917. To check which
458 build version you are running, you may open a command prompt on
459 Windows and execute the command "ver".
460 ::
461
462 C:\Users\myuser> ver
463
464 Microsoft Windows [Version 10.0.19041.153]
465
466 If your build is capable of running
467 WSLv2 you may continue, for more information on this subject or
468 instructions on how to upgrade to WSLv2 visit `Windows 10
469 WSLv2 <https://docs.microsoft.com/en-us/windows/wsl/wsl2-install>`__
470
4712. *Install the Linux distribution of your choice inside Windows 10:*
472 Once you know your version of Windows 10 supports WSLv2, you can
473 install the distribution of your choice from the Microsoft Store.
474 Open the Microsoft Store and search for Linux. While there are
475 several Linux distributions available, the assumption is that your
476 pick will be one of the distributions supported by the Yocto Project
477 as stated on the instructions for using a native Linux host. After
478 making your selection, simply click "Get" to download and install the
479 distribution.
480
4813. *Check your Linux distribution is using WSLv2:* Open a Windows
Andrew Geisslerc926e172021-05-07 16:11:35 -0500482 PowerShell and run::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500483
484 C:\WINDOWS\system32> wsl -l -v
485 NAME STATE VERSION
486 *Ubuntu Running 2
487
488 Note the version column which says the WSL version
489 being used by your distribution, on compatible systems, this can be
490 changed back at any point in time.
491
4924. *Optionally Orient Yourself on WSL:* If you are unfamiliar with WSL,
493 you can learn more here -
494 https://docs.microsoft.com/en-us/windows/wsl/wsl2-about.
495
4965. *Launch your WSL Distibution:* From the Windows start menu simply
497 launch your WSL distribution just like any other application.
498
4996. *Optimize your WSLv2 storage often:* Due to the way storage is
Patrick Williams975a06f2022-10-21 14:42:47 -0500500 handled on WSLv2, the storage space used by the underlying Linux
501 distribution is not reflected immediately, and since BitBake heavily
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500502 uses storage, after several builds, you may be unaware you are
503 running out of space. WSLv2 uses a VHDX file for storage, this issue
504 can be easily avoided by manually optimizing this file often, this
505 can be done in the following way:
506
Andrew Geissler9aee5002022-03-30 16:27:02 +0000507 1. *Find the location of your VHDX file:*
508
509 First you need to find the distro app package directory, to achieve this
510 open a Windows Powershell as Administrator and run::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500511
512 C:\WINDOWS\system32> Get-AppxPackage -Name "*Ubuntu*" | Select PackageFamilyName
513 PackageFamilyName
514 -----------------
515 CanonicalGroupLimited.UbuntuonWindows_79abcdefgh
516
517
518 You should now
519 replace the PackageFamilyName and your user on the following path
Andrew Geisslerc926e172021-05-07 16:11:35 -0500520 to find your VHDX file::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500521
Andrew Geissler9aee5002022-03-30 16:27:02 +0000522 ls C:\Users\myuser\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79abcdefgh\LocalState\
523 Mode LastWriteTime Length Name
524 -a---- 3/14/2020 9:52 PM 57418973184 ext4.vhdx
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500525
526 Your VHDX file path is:
527 ``C:\Users\myuser\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79abcdefgh\LocalState\ext4.vhdx``
528
Andrew Geissler9aee5002022-03-30 16:27:02 +0000529 2a. *Optimize your VHDX file using Windows Powershell:*
530
531 To use the ``optimize-vhd`` cmdlet below, first install the Hyper-V
532 option on Windows. Then, open a Windows Powershell as Administrator to
533 optimize your VHDX file, shutting down WSL first::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500534
535 C:\WINDOWS\system32> wsl --shutdown
536 C:\WINDOWS\system32> optimize-vhd -Path C:\Users\myuser\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79abcdefgh\LocalState\ext4.vhdx -Mode full
537
Andrew Geissler9aee5002022-03-30 16:27:02 +0000538 A progress bar should be shown while optimizing the
539 VHDX file, and storage should now be reflected correctly on the
540 Windows Explorer.
541
542 2b. *Optimize your VHDX file using DiskPart:*
543
544 The ``optimize-vhd`` cmdlet noted in step 2a above is provided by
545 Hyper-V. Not all SKUs of Windows can install Hyper-V. As an alternative,
546 use the DiskPart tool. To start, open a Windows command prompt as
547 Administrator to optimize your VHDX file, shutting down WSL first::
548
549 C:\WINDOWS\system32> wsl --shutdown
550 C:\WINDOWS\system32> diskpart
551
552 DISKPART> select vdisk file="<path_to_VHDX_file>"
553 DISKPART> attach vdisk readonly
554 DISKPART> compact vdisk
555 DISKPART> exit
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500556
557.. note::
558
559 The current implementation of WSLv2 does not have out-of-the-box
560 access to external devices such as those connected through a USB
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500561 port, but it automatically mounts your ``C:`` drive on ``/mnt/c/``
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500562 (and others), which you can use to share deploy artifacts to be later
563 flashed on hardware through Windows, but your build directory should
564 not reside inside this mountpoint.
565
566Once you have WSLv2 set up, everything is in place to develop just as if
567you were running on a native Linux machine. If you are going to use the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600568Extensible SDK container, see the ":doc:`/sdk-manual/extensible`" Chapter in the Yocto
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500569Project Application Development and the Extensible Software Development
570Kit (eSDK) manual. If you are going to use the Toaster container, see
Andrew Geissler09209ee2020-12-13 08:44:15 -0600571the ":doc:`/toaster-manual/setup-and-use`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500572section in the Toaster User Manual.
573
574Locating Yocto Project Source Files
575===================================
576
577This section shows you how to locate, fetch and configure the source
578files you'll need to work with the Yocto Project.
579
580.. note::
581
582 - For concepts and introductory information about Git as it is used
Andrew Geissler09209ee2020-12-13 08:44:15 -0600583 in the Yocto Project, see the ":ref:`overview-manual/development-environment:git`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500584 section in the Yocto Project Overview and Concepts Manual.
585
586 - For concepts on Yocto Project source repositories, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600587 ":ref:`overview-manual/development-environment:yocto project source repositories`"
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500588 section in the Yocto Project Overview and Concepts Manual."
589
590Accessing Source Repositories
591-----------------------------
592
Andrew Geissler09209ee2020-12-13 08:44:15 -0600593Working from a copy of the upstream :ref:`dev-manual/start:accessing source repositories` is the
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500594preferred method for obtaining and using a Yocto Project release. You
595can view the Yocto Project Source Repositories at
596:yocto_git:`/`. In particular, you can find the ``poky``
Andrew Geissler09209ee2020-12-13 08:44:15 -0600597repository at :yocto_git:`/poky`.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500598
599Use the following procedure to locate the latest upstream copy of the
600``poky`` Git repository:
601
6021. *Access Repositories:* Open a browser and go to
603 :yocto_git:`/` to access the GUI-based interface into the
604 Yocto Project source repositories.
605
6062. *Select the Repository:* Click on the repository in which you are
607 interested (e.g. ``poky``).
608
6093. *Find the URL Used to Clone the Repository:* At the bottom of the
610 page, note the URL used to clone that repository
Andrew Geissler09209ee2020-12-13 08:44:15 -0600611 (e.g. :yocto_git:`/poky`).
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500612
613 .. note::
614
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500615 For information on cloning a repository, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600616 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`" section.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500617
618Accessing Index of Releases
619---------------------------
620
621Yocto Project maintains an Index of Releases area that contains related
622files that contribute to the Yocto Project. Rather than Git
623repositories, these files are tarballs that represent snapshots in time
624of a given component.
625
626.. note::
627
628 The recommended method for accessing Yocto Project components is to
629 use Git to clone the upstream repository and work from within that
William A. Kennington IIIac69b482021-06-02 12:28:27 -0700630 locally cloned repository. However, this section documents how to
631 use a tarball snapshot of any given component.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500632
633Follow these steps to locate and download a particular tarball:
634
6351. *Access the Index of Releases:* Open a browser and go to
Andrew Geisslerc3d88e42020-10-02 09:45:00 -0500636 :yocto_dl:`Index of Releases </releases>`. The
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500637 list represents released components (e.g. ``bitbake``, ``sato``, and
638 so on).
639
640 .. note::
641
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500642 The ``yocto`` directory contains the full array of released Poky
643 tarballs. The ``poky`` directory in the Index of Releases was
644 historically used for very early releases and exists now only for
645 retroactive completeness.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500646
6472. *Select a Component:* Click on any released component in which you
648 are interested (e.g. ``yocto``).
649
6503. *Find the Tarball:* Drill down to find the associated tarball. For
651 example, click on ``yocto-&DISTRO;`` to view files associated with the
Andrew Geissler9aee5002022-03-30 16:27:02 +0000652 Yocto Project &DISTRO; release.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500653
6544. *Download the Tarball:* Click the tarball to download and save a
655 snapshot of the given component.
656
657Using the Downloads Page
658------------------------
659
660The :yocto_home:`Yocto Project Website <>` uses a "DOWNLOADS" page
661from which you can locate and download tarballs of any Yocto Project
662release. Rather than Git repositories, these files represent snapshot
663tarballs similar to the tarballs located in the Index of Releases
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500664described in the ":ref:`dev-manual/start:accessing index of releases`" section.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500665
Andrew Geisslerc9f78652020-09-18 14:11:35 -05006661. *Go to the Yocto Project Website:* Open The
667 :yocto_home:`Yocto Project Website <>` in your browser.
668
6692. *Get to the Downloads Area:* Select the "DOWNLOADS" item from the
670 pull-down "SOFTWARE" tab menu near the top of the page.
671
6723. *Select a Yocto Project Release:* Use the menu next to "RELEASE" to
673 display and choose a recent or past supported Yocto Project release
674 (e.g. &DISTRO_NAME_NO_CAP;, &DISTRO_NAME_NO_CAP_MINUS_ONE;, and so forth).
675
676 .. note::
677
678 For a "map" of Yocto Project releases to version numbers, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600679 :yocto_wiki:`Releases </Releases>` wiki page.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500680
681 You can use the "RELEASE ARCHIVE" link to reveal a menu of all Yocto
682 Project releases.
683
6844. *Download Tools or Board Support Packages (BSPs):* From the
685 "DOWNLOADS" page, you can download tools or BSPs as well. Just scroll
686 down the page and look for what you need.
687
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500688Cloning and Checking Out Branches
689=================================
690
691To use the Yocto Project for development, you need a release locally
692installed on your development system. This locally installed set of
693files is referred to as the :term:`Source Directory`
694in the Yocto Project documentation.
695
696The preferred method of creating your Source Directory is by using
Andrew Geissler09209ee2020-12-13 08:44:15 -0600697:ref:`overview-manual/development-environment:git` to clone a local copy of the upstream
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500698``poky`` repository. Working from a cloned copy of the upstream
699repository allows you to contribute back into the Yocto Project or to
700simply work with the latest software on a development branch. Because
701Git maintains and creates an upstream repository with a complete history
702of changes and you are working with a local clone of that repository,
703you have access to all the Yocto Project development branches and tag
704names used in the upstream repository.
705
706Cloning the ``poky`` Repository
707-------------------------------
708
709Follow these steps to create a local version of the upstream
710:term:`Poky` Git repository.
711
7121. *Set Your Directory:* Change your working directory to where you want
713 to create your local copy of ``poky``.
714
7152. *Clone the Repository:* The following example command clones the
716 ``poky`` repository and uses the default name "poky" for your local
Andrew Geisslerc926e172021-05-07 16:11:35 -0500717 repository::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500718
719 $ git clone git://git.yoctoproject.org/poky
720 Cloning into 'poky'...
721 remote: Counting objects: 432160, done.
722 remote: Compressing objects: 100% (102056/102056), done.
723 remote: Total 432160 (delta 323116), reused 432037 (delta 323000)
724 Receiving objects: 100% (432160/432160), 153.81 MiB | 8.54 MiB/s, done.
725 Resolving deltas: 100% (323116/323116), done.
726 Checking connectivity... done.
727
728 Unless you
729 specify a specific development branch or tag name, Git clones the
730 "master" branch, which results in a snapshot of the latest
731 development changes for "master". For information on how to check out
732 a specific development branch or on how to check out a local branch
Andrew Geissler3b8a17c2021-04-15 15:55:55 -0500733 based on a tag name, see the
734 ":ref:`dev-manual/start:checking out by branch in poky`" and
735 ":ref:`dev-manual/start:checking out by tag in poky`" sections, respectively.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500736
737 Once the local repository is created, you can change to that
William A. Kennington IIIac69b482021-06-02 12:28:27 -0700738 directory and check its status. The ``master`` branch is checked out
739 by default::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500740
Andrew Geissler95ac1b82021-03-31 14:34:31 -0500741 $ cd poky
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500742 $ git status
743 On branch master
744 Your branch is up-to-date with 'origin/master'.
745 nothing to commit, working directory clean
746 $ git branch
747 * master
748
749 Your local repository of poky is identical to the
750 upstream poky repository at the time from which it was cloned. As you
751 work with the local branch, you can periodically use the
752 ``git pull --rebase`` command to be sure you are up-to-date
753 with the upstream branch.
754
755Checking Out by Branch in Poky
756------------------------------
757
758When you clone the upstream poky repository, you have access to all its
759development branches. Each development branch in a repository is unique
760as it forks off the "master" branch. To see and use the files of a
761particular development branch locally, you need to know the branch name
762and then specifically check out that development branch.
763
764.. note::
765
766 Checking out an active development branch by branch name gives you a
767 snapshot of that particular branch at the time you check it out.
768 Further development on top of the branch that occurs after check it
769 out can occur.
770
7711. *Switch to the Poky Directory:* If you have a local poky Git
772 repository, switch to that directory. If you do not have the local
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500773 copy of poky, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600774 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500775 section.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500776
7772. *Determine Existing Branch Names:*
778 ::
779
780 $ git branch -a
781 * master
782 remotes/origin/1.1_M1
783 remotes/origin/1.1_M2
784 remotes/origin/1.1_M3
785 remotes/origin/1.1_M4
786 remotes/origin/1.2_M1
787 remotes/origin/1.2_M2
788 remotes/origin/1.2_M3
789 . . .
790 remotes/origin/thud
791 remotes/origin/thud-next
792 remotes/origin/warrior
793 remotes/origin/warrior-next
794 remotes/origin/zeus
795 remotes/origin/zeus-next
796 ... and so on ...
797
7983. *Check out the Branch:* Check out the development branch in which you
799 want to work. For example, to access the files for the Yocto Project
Andrew Geisslerc926e172021-05-07 16:11:35 -0500800 &DISTRO; Release (&DISTRO_NAME;), use the following command::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500801
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500802 $ git checkout -b &DISTRO_NAME_NO_CAP; origin/&DISTRO_NAME_NO_CAP;
803 Branch &DISTRO_NAME_NO_CAP; set up to track remote branch &DISTRO_NAME_NO_CAP; from origin.
804 Switched to a new branch '&DISTRO_NAME_NO_CAP;'
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500805
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500806 The previous command checks out the "&DISTRO_NAME_NO_CAP;" development
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500807 branch and reports that the branch is tracking the upstream
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500808 "origin/&DISTRO_NAME_NO_CAP;" branch.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500809
810 The following command displays the branches that are now part of your
811 local poky repository. The asterisk character indicates the branch
Andrew Geisslerc926e172021-05-07 16:11:35 -0500812 that is currently checked out for work::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500813
814 $ git branch
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500815 master
816 * &DISTRO_NAME_NO_CAP;
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500817
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500818Checking Out by Tag in Poky
819---------------------------
820
821Similar to branches, the upstream repository uses tags to mark specific
822commits associated with significant points in a development branch (i.e.
823a release point or stage of a release). You might want to set up a local
824branch based on one of those points in the repository. The process is
825similar to checking out by branch name except you use tag names.
826
827.. note::
828
829 Checking out a branch based on a tag gives you a stable set of files
830 not affected by development on the branch above the tag.
831
8321. *Switch to the Poky Directory:* If you have a local poky Git
833 repository, switch to that directory. If you do not have the local
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500834 copy of poky, see the
Andrew Geissler09209ee2020-12-13 08:44:15 -0600835 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
Andrew Geissler4c19ea12020-10-27 13:52:24 -0500836 section.
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500837
8382. *Fetch the Tag Names:* To checkout the branch based on a tag name,
Andrew Geisslerc926e172021-05-07 16:11:35 -0500839 you need to fetch the upstream tags into your local repository::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500840
841 $ git fetch --tags
842 $
843
Andrew Geisslerc926e172021-05-07 16:11:35 -05008443. *List the Tag Names:* You can list the tag names now::
Andrew Geisslerc9f78652020-09-18 14:11:35 -0500845
846 $ git tag
847 1.1_M1.final
848 1.1_M1.rc1
849 1.1_M1.rc2
850 1.1_M2.final
851 1.1_M2.rc1
852 .
853 .
854 .
855 yocto-2.5
856 yocto-2.5.1
857 yocto-2.5.2
858 yocto-2.5.3
859 yocto-2.6
860 yocto-2.6.1
861 yocto-2.6.2
862 yocto-2.7
863 yocto_1.5_M5.rc8
864
865
8664. *Check out the Branch:*
867 ::
868
869 $ git checkout tags/yocto-&DISTRO; -b my_yocto_&DISTRO;
870 Switched to a new branch 'my_yocto_&DISTRO;'
871 $ git branch
872 master
873 * my_yocto_&DISTRO;
874
875 The previous command creates and
876 checks out a local branch named "my_yocto_&DISTRO;", which is based on
877 the commit in the upstream poky repository that has the same tag. In
878 this example, the files you have available locally as a result of the
879 ``checkout`` command are a snapshot of the "&DISTRO_NAME_NO_CAP;"
880 development branch at the point where Yocto Project &DISTRO; was
881 released.