Lines Matching +full:directory +full:- +full:based
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
38 Linus Torvalds in 1991. Conversely, a good example of a non-open source
55 system not intended to run the software - the development host.
61 development host. When you have a Mac or Windows-based system, you can
63 `CROPS <https://github.com/crops/poky-container>`__, which leverages
66 environment that is similar to what you see when using a Linux-based
69 ":ref:`dev-manual/start:setting up to use cross platforms (crops)`"
80 ":ref:`dev-manual/start:setting up a native linux host`"
86 - *Command Lines, BitBake, and Shells:* Traditional development in the
89 BitBake, in a command-line environment from a shell on your
93 within a shell-based environment using components and tools available
97 ":ref:`dev-manual/common-tasks:building a simple image`"
100 - *Board Support Package (BSP) Development:* Development of BSPs
106 The :doc:`/bsp-guide/index` provides BSP-related development
108 ":ref:`bsp-guide/bsp:preparing your build host to work with bsp layers`"
112 - *Kernel Development:* If you are going to be developing kernels using
117 The :doc:`/kernel-dev/index` provides kernel-related
120 ":ref:`kernel-dev/common:preparing the build host to work on the kernel`"
123 - *Using Toaster:* The other Yocto Project development method that
133 :doc:`/toaster-manual/index`.
139 Yocto Project files at :yocto_git:`/`. This web-based source
145 the :term:`Source Directory`, which
158 - The recommended method for setting up the Yocto Project
159 :term:`Source Directory` and the files
160 for supported BSPs (e.g., ``meta-intel``) is to use
161 :ref:`overview-manual/development-environment:git`
164 - Be sure to always work in matching branches for both the selected
165 BSP repository and the Source Directory (i.e. ``poky``)
167 branch of ``poky`` and you are going to use ``meta-intel``, be
168 sure to checkout the "&DISTRO_NAME_NO_CAP;" branch of ``meta-intel``.
173 - :yocto_git:`Source Repositories: <>` This area contains IDE
178 .. image:: figures/source-repos.png
182 see the ":ref:`dev-manual/start:accessing source repositories`"
185 - :yocto_dl:`Index of /releases: </releases>` This is an index
186 of releases such as Poky, Pseudo, installers for cross-development
192 .. image:: figures/index-downloads.png
196 ":ref:`dev-manual/start:accessing index of releases`"
199 - *"DOWNLOADS" page for the* :yocto_home:`Yocto Project Website <>` *:*
207 .. image:: figures/yp-download.png
211 ":ref:`dev-manual/start:using the downloads page`"
218 :ref:`overview-manual/development-environment:git`.
247 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
251 contribution Git repository named ``poky-contrib``. You can see all the
267 Developers are responsible for keeping their local repository up-to-date
279 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
289 .. image:: svg/git-workflow.*
296 Book <https://book.git-scm.com>`__.
298 - *Make Small Changes:* It is best to keep the changes you commit small
303 - *Make Complete Changes:* It is also good practice to leave the
309 - *Use Branches Liberally:* It is very easy to create, use, and delete
317 - *Merge Changes:* The ``git merge`` command allows you to take the
325 - *Manage Branches:* Because branches are easy to use, you should use a
330 you can merge code across the branches to reflect ever-increasing
333 - *Use Push and Pull:* The push-pull workflow is based on the concept
335 is usually a contribution repository. This workflow is also based on
341 ``create-pull-request`` and ``send-pull-request`` that ship with the
344 :term:`Source Directory`. For information
346 ":ref:`dev-manual/common-tasks:using scripts to push a change upstream and request a pull`"
349 - *Patch Workflow:* This workflow allows you to notify the maintainer
353 using the Git commands ``git format-patch`` and ``git send-email``.
355 ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`"
363 development, non-linear development, and can handle large projects. It
372 - For more information on Git, see
373 https://git-scm.com/documentation.
375 - If you need to download Git, it is recommended that you add Git to
378 page, see https://git-scm.com/download.
380 - For information beyond the introductory nature in this section,
381 see the ":ref:`dev-manual/start:locating yocto project source files`"
385 --------------------------------
388 ":ref:`overview-manual/development-environment:git workflows and the yocto project`"
390 If you look at this web-interface of the repositories, each item is a separate
395 Creating a tree-like structure based on project divergence allows for
412 ":ref:`dev-manual/start:locating yocto project source files`"
436 $ git clone git://git.yoctoproject.org/poky -b &DISTRO_NAME_NO_CAP;
439 after moving to the home directory, the ``git clone`` command creates a
447 working branch based on a branch name, your local environment matches
451 checking out a local branch based on the "&DISTRO_NAME_NO_CAP;" branch
462 Some key tags for the ``poky`` repository are ``jethro-14.0.3``,
463 ``morty-16.0.1``, ``pyro-17.0.0``, and
464 ``&DISTRO_NAME_NO_CAP;-&DISTRO;``. These tags represent Yocto Project
469 create and checkout a local working Git branch based on a tag name. When
478 $ git fetch --tags
479 $ git checkout tags/rocko-18.0.0 -b my_rocko-18.0.0
482 of the top-level directory of your local Yocto Project repository is
483 ``poky``. After moving to the ``poky`` directory, the ``git fetch``
486 a branch named "my-rocko-18.0.0" that is based on the upstream branch
488 "rocko-18.0.0" tag. The files in your repository now exactly match that
491 checkout a local working branch based on a tag, your environment matches
496 --------------
504 `here <https://git-scm.com/documentation>`__.
512 - *git init:* Initializes an empty Git repository. You cannot use
515 - *git clone:* Creates a local clone of a Git repository that is on
519 - *git add:* Locally stages updated file contents to the index that
523 - *git commit:* Creates a local "commit" that documents the changes
530 - *git status:* Reports any modified files that possibly need to be
534 - *git checkout branch-name:* Changes your local working branch and
538 - *git checkout -b working-branch upstream-branch:* Creates and
545 - *git branch:* Displays the existing local branches associated
549 - *git branch -D branch-name:* Deletes an existing local branch.
551 in order to delete branch-name.
553 - *git pull \-\-rebase*: Retrieves information from an upstream Git
557 branch). The ``--rebase`` option ensures that any local commits you
560 - *git push repo-name local-branch:upstream-branch:* Sends
567 - *git merge:* Combines or adds changes from one local branch of
570 workflow is to create a temporary branch that is based off "main"
579 - *git cherry-pick commits:* Choose and apply specific commits from
584 - *gitk:* Provides a GUI view of the branches and changes in your
594 - *git log:* Reports a history of your commits to the repository.
598 - *git diff:* Displays line-by-line differences between a local
610 - `Open source license
611 history <https://en.wikipedia.org/wiki/Open-source_license>`__
613 - `Free software license
623 `here <https://www.opensource.org/licenses/mit-license.php>`__. You can
625 `here <https://www.opensource.org/licenses/LGPL-3.0>`__.
629 the :term:`Source Directory` at
630 ``meta/files/common-licenses``. Once the build completes, the list of
632 :term:`Build Directory` at
652 Project uses in the ``meta/files/common-licenses`` directory in your
653 :term:`Source Directory`.
658 ":ref:`dev-manual/common-tasks:maintaining open source license compliance during your product's lif…