Lines Matching full:development

14 Creating a Team Development Environment
18 team development environment, or how to scale it for a large team of
36     equipment together and set up your development environment's
53        system development meets desired quality standards.
56     get the hardware together. Ideally, any development, build, or test
66        building Yocto Project development containers to be run under
71     can understand the hardware topology of the development environment.
73     development environment.
81     :ref:`overview-manual/development-environment:git`.
112 5.  *Set up the Application Development Machines:* As mentioned earlier,
115     machines used for application development:
122     -  Keep your cross-development toolchains updated. You can do this
129        locations to allow development across versions.
131 6.  *Set up the Core Development Machines:* As mentioned earlier, core
149     development environment. It is here that changes from individual
189     develop locally using their primary development system.
204     As with any development environment, it is important to document the
216 10. *Development Environment Summary:* Aside from the previous steps,
217     here are best practices within the Yocto Project development
220     -  Use :ref:`overview-manual/development-environment:git` as the source control
230 …repositories. See the ":ref:`overview-manual/development-environment:yocto project source reposito…
266 development using the Yocto Project. Your build host can be a native
284 Package (BSP) development and kernel development:
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…
291    section in the Yocto Project Linux Kernel Development Manual.
330 4. *Install Development Host Packages:* Required development host
340 using a given development path on your native Linux machine. If you are
345 Project Application Development and the Extensible Software Development
355 create a Yocto Project development environment that is operating system
419    development host.
437 Project Application Development and the Extensible Software Development
447 you can create a Yocto Project development environment that allows you
567 Project Application Development and the Extensible Software Development
581       in the Yocto Project, see the ":ref:`overview-manual/development-environment:git`"
585       ":ref:`overview-manual/development-environment:yocto project source repositories`"
689 To use the Yocto Project for development, you need a release locally
690 installed on your development system. This locally installed set of
695 :ref:`overview-manual/development-environment:git` to clone a local copy of the upstream
698 simply work with the latest software on a development branch. Because
701 you have access to all the Yocto Project development branches and tag
727    specify a specific development branch or tag name, Git clones the
729    development changes for "master". For information on how to check out
730    a specific development branch or on how to check out a local branch
757 development branches. Each development branch in a repository is unique
759 particular development branch locally, you need to know the branch name
760 and then specifically check out that development branch.
764    Checking out an active development branch by branch name gives you a
766    Further development on top of the branch that occurs after check it
796 3. *Check out the Branch:* Check out the development branch in which you
804    The previous command checks out the "&DISTRO_NAME_NO_CAP;" development
820 commits associated with significant points in a development branch (i.e.
828    not affected by development on the branch above the tag.
878    development branch at the point where Yocto Project &DISTRO; was