Lines Matching +full:debian +full:- +full:testing
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
10 host <dev-manual/start:preparing the build host>`, how to locate
25 you get the results you want. The procedure is high-level and presents
41 - *Application Developer:* This type of developer does application
44 - *Core System Developer:* This type of developer works on the
47 - *Build Engineer:* This type of developer manages Autobuilders and
51 - *Test Engineer:* This type of developer creates and manages
55 2. *Gather the Hardware:* Based on the size and make-up of the team,
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
70 understand the hardware involved and the make-up of the team, you
81 :ref:`overview-manual/development-environment:git`.
96 branch-based access controls to repositories that you can control as
104 - `Gitolite <https://gitolite.com>`__: Information for
107 - `Interfaces, frontends, and
117 - Use a pre-built toolchain that contains the software stack
122 - Keep your cross-development toolchains updated. You can do this
128 - Use multiple toolchains installed locally into different
136 - Have the :term:`OpenEmbedded Build System` available on
140 - Keep the core system unchanged as much as possible and do your
145 - Share layers amongst the developers of a particular project and
153 integration" style testing of software components and regression
164 - Highlights when commits break the build.
166 - Populates an :ref:`sstate
167 cache <overview-manual/concepts:shared state cache>` from which
170 - Allows commit hook triggers, which trigger builds when commits
173 - Allows triggering of automated image booting and testing under
176 - Supports incremental build testing and from-scratch builds.
178 - Shares output that allows developer testing and historical
181 - Creates output that can be used for releases.
183 - Allows scheduling of builds so that resources can be used
187 performance systems for testing purposes. Developers can use these
188 systems for wider, more extensive testing while they continue to
193 send pull requests (i.e. ``create-pull-request`` and
194 ``send-pull-request``). This model is in line with other open source
196 project and a single maintainer handles the final "top-of-tree"
207 well-structured commit messages, which are usually a part of a
220 - Use :ref:`overview-manual/development-environment:git` as the source control
223 - Maintain your Metadata in layers that make sense for your
224 situation. See the ":ref:`overview-manual/yp-intro:the yocto project layer model`"
226 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
229 - Separate the project's Metadata and code by using separate Git
230 …repositories. See the ":ref:`overview-manual/development-environment:yocto project source reposito…
233 ":ref:`dev-manual/start:locating yocto project source files`"
237 - Set up the directory for the shared state cache
243 - Set up an Autobuilder and have it populate the sstate cache and
246 - The Yocto Project community encourages you to send patches to the
250 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
253 - Send changes to the core sooner than later as others are likely
256 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
258 of the available mailing lists, see the ":ref:`resources-mailinglist`" section in
268 Windows) that uses `CROPS <https://github.com/crops/poky-container>`__,
279 `WSLv2 <https://docs.microsoft.com/en-us/windows/wsl/install-win10>`__.
286 - *BSP Development:* See the ":ref:`bsp-guide/bsp:preparing your build host to work with bsp layer…
290 - *Kernel Development:* See the ":ref:`kernel-dev/common:preparing the build host to work on the k…
294 ------------------------------
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
305 Distributions <detailed-supported-distros>`"
316 - Git &MIN_GIT_VERSION; or greater
318 - tar &MIN_TAR_VERSION; or greater
320 - Python &MIN_PYTHON_VERSION; or greater.
322 - gcc &MIN_GCC_VERSION; or greater.
327 ":ref:`ref-manual/system-requirements:required git, tar, python and gcc versions`"
336 ":ref:`ref-manual/system-requirements:required packages for the build host`"
342 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
344 to use the Extensible SDK, see the ":doc:`/sdk-manual/extensible`" Chapter in the Yocto
346 Kit (eSDK) manual. If you want to work on the kernel, see the :doc:`/kernel-dev/index`. If you are …
347 Toaster, see the ":doc:`/toaster-manual/setup-and-use`"
351 -----------------------------------------
353 With `CROPS <https://github.com/crops/poky-container>`__, which
363 `Docker <https://www.docker.com/what-docker>`__ is a software
368 Platforms <https://docs.docker.com/engine/install/#supported-platforms>`__"
375 Pre-Windows 10 or Windows 10 "Home" version), you must install Docker
385 pre-requisites, you can download and install the appropriate
389 - Install `Docker Desktop on
390 … Windows <https://docs.docker.com/docker-for-windows/install/#install-docker-desktop-on-windows>`__
393 - Install `Docker Desktop on
394 … MacOs <https://docs.docker.com/docker-for-mac/install/#install-and-run-docker-desktop-on-mac>`__
397 - Install `Docker Engine on
401 - Install `Docker Engine on
402 Debian <https://docs.docker.com/engine/install/debian/>`__
403 for Linux build hosts running the Debian distribution.
405 - Install `Docker Engine for
409 - Install `Docker Engine for
414 Docker and the container concept, you can learn more here -
415 https://docs.docker.com/get-started/.
422 https://github.com/crops/docker-win-mac-docs/wiki and follow
434 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
436 ":doc:`/sdk-manual/extensible`" Chapter in the Yocto
439 the ":doc:`/toaster-manual/setup-and-use`"
443 -----------------------------------------------------
446 (WSLv2) <https://docs.microsoft.com/en-us/windows/wsl/wsl2-about>`__,
467 WSLv2 <https://docs.microsoft.com/en-us/windows/wsl/wsl2-install>`__
482 C:\WINDOWS\system32> wsl -l -v
491 you can learn more here -
492 https://docs.microsoft.com/en-us/windows/wsl/wsl2-about.
510 C:\WINDOWS\system32> Get-AppxPackage -Name "*Ubuntu*" | Select PackageFamilyName
512 -----------------
522 -a---- 3/14/2020 9:52 PM 57418973184 ext4.vhdx
529 To use the ``optimize-vhd`` cmdlet below, first install the Hyper-V
533 C:\WINDOWS\system32> wsl --shutdown
534 …stem32> optimize-vhd -Path C:\Users\myuser\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWi…
542 The ``optimize-vhd`` cmdlet noted in step 2a above is provided by
543 Hyper-V. Not all SKUs of Windows can install Hyper-V. As an alternative,
547 C:\WINDOWS\system32> wsl --shutdown
557 The current implementation of WSLv2 does not have out-of-the-box
566 Extensible SDK container, see the ":doc:`/sdk-manual/extensible`" Chapter in the Yocto
569 the ":doc:`/toaster-manual/setup-and-use`"
580 - For concepts and introductory information about Git as it is used
581 in the Yocto Project, see the ":ref:`overview-manual/development-environment:git`"
584 - For concepts on Yocto Project source repositories, see the
585 ":ref:`overview-manual/development-environment:yocto project source repositories`"
589 -----------------------------
591 Working from a copy of the upstream :ref:`dev-manual/start:accessing source repositories` is the
601 :yocto_git:`/` to access the GUI-based interface into the
614 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`" section.
617 ---------------------------
649 example, click on ``yocto-&DISTRO;`` to view files associated with the
656 ------------------------
662 described in the ":ref:`dev-manual/start:accessing index of releases`" section.
668 pull-down "SOFTWARE" tab menu near the top of the page.
695 :ref:`overview-manual/development-environment:git` to clone a local copy of the upstream
705 -------------------------------
732 ":ref:`dev-manual/start:checking out by branch in poky`" and
733 ":ref:`dev-manual/start:checking out by tag in poky`" sections, respectively.
742 Your branch is up-to-date with 'origin/master'.
750 ``git pull --rebase`` command to be sure you are up-to-date
754 ------------------------------
772 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
778 $ git branch -a
789 remotes/origin/thud-next
791 remotes/origin/warrior-next
793 remotes/origin/zeus-next
800 $ git checkout -b &DISTRO_NAME_NO_CAP; origin/&DISTRO_NAME_NO_CAP;
817 ---------------------------
833 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
839 $ git fetch --tags
853 yocto-2.5
854 yocto-2.5.1
855 yocto-2.5.2
856 yocto-2.5.3
857 yocto-2.6
858 yocto-2.6.1
859 yocto-2.6.2
860 yocto-2.7
867 $ git checkout tags/yocto-&DISTRO; -b my_yocto_&DISTRO;