| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/orm/fixtures/ |
| H A D | oe-core.xml | 1 <?xml version="1.0" encoding="utf-8"?>
2 <django-objects version="1.0">
3 <!-- Set the project default value for DISTRO -->
9 <!-- Bitbake versions which correspond to the metadata release -->
12 <field type="CharField" name="giturl">git://git.openembedded.org/bitbake</field>
17 <field type="CharField" name="giturl">git://git.openembedded.org/bitbake</field>
22 <field type="CharField" name="giturl">git://git.openembedded.org/bitbake</field>
27 <field type="CharField" name="giturl">git://git.openembedded.org/bitbake</field>
32 <field type="CharField" name="giturl">git://git.openembedded.org/bitbake</field>
36 <!-- Releases available -->
[all …]
|
| H A D | gen_fixtures.py | 3 # -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
5 # Generate Toaster Fixtures for 'poky.xml' and 'oe-core.xml'
8 # SPDX-License-Identifier: GPL-2.0-only
38 … ['Kirkstone','3.5','April 2022','','Future - Long Term Support (until Apr. 2024)','27.0','1.54'],
39 # ['Dunfell','3.1','April 2021','3.1.5 (March 2022)','Stable - Support for 13 months (until Apr.…
48 …['Hardknott','3.3','April 2021','3.3.5 (March 2022)','Stable - Support for 13 months (until Apr. 2…
52 'openembedded-core',
53 'meta-poky',
54 'meta-yocto-bsp',
58 'openembedded-core',
[all …]
|
| /OK3568_Linux_fs/yocto/poky/ |
| H A D | README.md | 4 Poky is an integration of various components to form a pre-packaged
9 to Weston, commandline and more. The system supports cross-architecture
17 [layer index](https://layers.openembedded.org/).
20 [BitBake](https://git.openembedded.org/bitbake/),
21 [OpenEmbedded-Core](https://git.openembedded.org/openembedded-core/),
22 [Yocto documentation](https://git.yoctoproject.org/cgit.cgi/yocto-docs/),
23 the '[meta-yocto](https://git.yoctoproject.org/cgit.cgi/meta-yocto/)' layer
25 are all part of the Yocto Project and OpenEmbedded ecosystems.
30 OpenEmbedded is the build architecture used by Poky and the Yocto project.
31 For information about OpenEmbedded, see the
[all …]
|
| H A D | README.poky.md | 4 Poky is an integration of various components to form a pre-packaged
9 to Weston, commandline and more. The system supports cross-architecture
17 [layer index](https://layers.openembedded.org/).
20 [BitBake](https://git.openembedded.org/bitbake/),
21 [OpenEmbedded-Core](https://git.openembedded.org/openembedded-core/),
22 [Yocto documentation](https://git.yoctoproject.org/cgit.cgi/yocto-docs/),
23 the '[meta-yocto](https://git.yoctoproject.org/cgit.cgi/meta-yocto/)' layer
25 are all part of the Yocto Project and OpenEmbedded ecosystems.
30 OpenEmbedded is the build architecture used by Poky and the Yocto project.
31 For information about OpenEmbedded, see the
[all …]
|
| H A D | README.OE-Core.md | 1 OpenEmbedded-Core chapter
4 OpenEmbedded-Core is a layer containing the core metadata for current versions
5 of OpenEmbedded. It is distro-less (can build a functional image with
8 For information about OpenEmbedded, see the OpenEmbedded website:
9 https://www.openembedded.org/
17 ------------
20 https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
25 https://lists.openembedded.org/g/openembedded-core
29 https://git.openembedded.org/openembedded-core/
|
| /OK3568_Linux_fs/yocto/poky/meta-poky/ |
| H A D | README.poky.md | 4 Poky is an integration of various components to form a pre-packaged
9 to Weston, commandline and more. The system supports cross-architecture
17 [layer index](https://layers.openembedded.org/).
20 [BitBake](https://git.openembedded.org/bitbake/),
21 [OpenEmbedded-Core](https://git.openembedded.org/openembedded-core/),
22 [Yocto documentation](https://git.yoctoproject.org/cgit.cgi/yocto-docs/),
23 the '[meta-yocto](https://git.yoctoproject.org/cgit.cgi/meta-yocto/)' layer
25 are all part of the Yocto Project and OpenEmbedded ecosystems.
30 OpenEmbedded is the build architecture used by Poky and the Yocto project.
31 For information about OpenEmbedded, see the
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/overview-manual/ |
| H A D | yp-intro.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 developers create custom Linux-based systems that are designed for
26 .. image:: figures/key-dev-elements.png
31 …ticle <https://www.embedded.com/electronics-blogs/say-what-/4458600/Why-the-Yocto-Project-for-my-I…
39 --------
43 - *Widely Adopted Across the Industry:* Many semiconductor, operating
50 - *Architecture Agnostic:* Yocto Project supports Intel, ARM, MIPS,
59 - *Images and Code Transfer Easily:* Yocto Project output can easily
68 - *Flexibility:* Corporations use the Yocto Project many different
75 - *Ideal for Constrained Embedded and IoT devices:* Unlike a full Linux
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/layerindexlib/tests/ |
| H A D | cooker.py | 3 # SPDX-License-Identifier: GPL-2.0-only
40 (dependencies, invalidnames) = self.layerindex.find_dependencies(names=['meta-python'])
52 # Top of the deps should be openembedded-core, since everything depends on it.
53 …self.assertEqual(layerBranch.layer.name, "openembedded-core", msg='Top dependency not openembedded…
55 # meta-python should cause an openembedded-core dependency, if not assert!
57 if dep.layer.name == 'meta-python':
60 self.assertTrue(False, msg='meta-python was not found')
71 … self.assertEqual(layerBranch.layer.name, "meta-python", msg='Last dependency not meta-python')
82 tests = [ ('core', True),
83 ('openembedded-core', False),
[all …]
|
| H A D | restapi.py | 1 # Copyright (C) 2017-2018 Wind River Systems, Inc.
3 # SPDX-License-Identifier: GPL-2.0-only
25 …self.layerindex.load_layerindex('https://layers.openembedded.org/layerindex/api/;branch=sumo', loa…
94 (dependencies, invalidnames) = self.layerindex.find_dependencies(names=['meta-python'])
106 # Top of the deps should be openembedded-core, since everything depends on it.
107 …self.assertEqual(layerBranch.layer.name, "openembedded-core", msg='OpenEmbedded-Core is no the fir…
109 # meta-python should cause an openembedded-core dependency, if not assert!
111 if dep.layer.name == 'meta-python':
114 self.logger.debug("meta-python was not found")
126 … self.assertEqual(layerBranch.layer.name, "meta-python", msg="Last dependency not meta-python")
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | terms.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
15 known as BitBake append files and ``.bbappend`` files. The OpenEmbedded
23 similarly-named recipe file. For an example of an append file in use, see
24 the ":ref:`dev-manual/common-tasks:appending other layers metadata with your layer`"
37 .. code-block:: shell
53 The task executor and scheduler used by the OpenEmbedded build system to
60 the :doc:`/bsp-guide/index`.
63 This term refers to the area used by the OpenEmbedded build system for
66 (i.e. :ref:`ref-manual/structure:\`\`oe-init-build-env\`\``). The
73 - Create the Build Directory inside your Source Directory and let
[all …]
|
| H A D | structure.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
15 ":ref:`dev-manual/start:locating yocto project source files`"
20 The OpenEmbedded build system does not support file or directory
24 .. _structure-core:
26 Top-Level Core Components
29 This section describes the top-level components of the :term:`Source Directory`.
31 .. _structure-core-bitbake:
34 ------------
45 environment setup script (i.e. :ref:`structure-core-script`) places
52 .. _structure-core-build:
[all …]
|
| H A D | faq.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 **Q:** How does Poky differ from :oe_home:`OpenEmbedded <>`?
11 :term:`OpenEmbedded-Core (OE-Core)` and :term:`BitBake`. Thus, the
12 generic term used here for the build system is the "OpenEmbedded build
14 OpenEmbedded, with changes always being merged to OE-Core or BitBake
25 ":ref:`ref-manual/system-requirements:required git, tar, python and gcc versions`"
28 **Q:** How can you claim Poky / OpenEmbedded-Core is stable?
32 - The Yocto Project team keeps :term:`OpenEmbedded-Core (OE-Core)` small and
34 available in other OpenEmbedded community layers. Keeping it small
37 - The Yocto Project team runs manual and automated tests using a small,
[all …]
|
| H A D | resources.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 .. _resources-intro:
17 .. _resources-contributions:
26 code, see the ":ref:`dev-manual/common-tasks:submitting a change to the yocto project`" section in …
29 .. _resources-bugtracker:
49 - The ":ref:`dev-manual/common-tasks:submitting a defect against the yocto project`"
52 - The Yocto Project :yocto_wiki:`Bugzilla wiki page </Bugzilla_Configuration_and_Bug_Tracking>`
56 .. _resources-mailinglist:
62 as related OpenEmbedded mailing lists for discussion, patch submission
67 - :yocto_lists:`/g/yocto` - General Yocto Project
[all …]
|
| /OK3568_Linux_fs/yocto/poky/bitbake/ |
| H A D | README | 5 efficiently and in parallel while working within complex inter-task dependency constraints.
6 One of BitBake's main users, OpenEmbedded, takes this core and builds embedded Linux software
7 stacks using a task-oriented approach.
9 For information about Bitbake, see the OpenEmbedded website:
10 https://www.openembedded.org/
17 ------------
20 https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
22 for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org)
24 the patch is through git-send-email. For example, to send the last commit (HEAD) on current
27 git send-email -M -1 --to bitbake-devel@lists.openembedded.org
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/ |
| H A D | README | 1 meta-networking
4 This layer is intended to be a central point for networking-related
6 oe-core and compliments meta-openembedded. It should be primarily useful
9 - Anyone building a small networking device (eg. a home router /
12 - Anyone wanting to add network services to their device (eg.
16 ------------
20 URI: git://git.openembedded.org/openembedded-core
23 For some recipes, the meta-oe layer is required:
25 URI: git://git.openembedded.org/meta-openembedded
26 subdirectory: meta-oe
[all …]
|
| /OK3568_Linux_fs/yocto/meta-clang/ |
| H A D | README.md | 1 …I](https://github.com/kraj/meta-clang/workflows/Yoe%20Distro%20CI/badge.svg?branch=master)](https:…
3 # meta-clang (C/C++ frontend and LLVM compiler backend)
6 C/C++ compiler for OpenEmbedded/Yocto Project based distributions. This can cohabit
12 git clone git://github.com/openembedded/openembedded-core.git
13 cd openembedded-core
14 git clone git://github.com/openembedded/bitbake.git
15 git clone git://github.com/kraj/meta-clang.git
17 $ . ./oe-init-build-env
24 git clone git://github.com/kraj/meta-clang.git
26 $ . ./oe-init-build-env
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/bsp-guide/ |
| H A D | bsp.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Board Support Packages (BSP) - Developer's Guide
19 Layer using the :ref:`bitbake-layers <bsp-guide/bsp:Creating a new BSP Layer Using the \`\`bitbake-…
28 layers in the Yocto Project use the following well-established naming
31 meta-bsp_root_name
33 The string "meta-" is prepended to the
38 Because the BSP layer naming convention is well-established, it is
40 BSP layer name does not need to start with ``meta-``.
47 :ref:`overview-manual/development-environment:yocto project source repositories`
58 ``meta-raspberrypi`` and ``meta-intel``). Each of these layers is a
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/ |
| H A D | README | 1 meta-perl
3 This layer provides commonly-used perl related recipes such as perl libraries
7 -----------------
12 -- libdbi-perl --
17 |<- Scope of DBI ->|
18 .-. .--------------. .-------------.
19 .-------. | |---| XYZ Driver |---| XYZ Engine |
20 | Perl | | | `--------------' `-------------'
21 | script| |A| |D| .--------------. .-------------.
22 | using |--|P|--|B|---|Oracle Driver |---|Oracle Engine|
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-multimedia/ |
| H A D | README | 3 URI: git://git.openembedded.org/openembedded-core
6 URI: git://git.openembedded.org/meta-openembedded
7 layers: meta-oe
10 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia][kirkstone]'…
13 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-multimed…
15 You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded t…
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-gnome/ |
| H A D | README | 2 ------------
5 URI: git://git.openembedded.org/openembedded-core
8 URI: git://git.openembedded.org/meta-openembedded
11 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-gnome][kirkstone]' in t…
14 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-gnome][k…
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-python/ |
| H A D | README | 1 meta-python
5 -------------------------
7 This layer is intended to be the home of python modules for OpenEmbedded.
10 -------------------------
12 The meta-python layer depends on:
14 URI: git://git.openembedded.org/openembedded-core
18 URI: git://git.openembedded.org/meta-openembedded
19 layers: meta-oe
24 http://www.angstrom-distribution.org/building-angstrom,
28 -------------------------
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-xfce/ |
| H A D | README | 3 URI: git://git.openembedded.org/openembedded-core
6 URI: git://git.openembedded.org/meta-openembedded
9 meta-xfce depends on meta-oe, meta-gnome and meta-multimedia in this repository.
11 To avoid dependencies on meta-multimedia you need to mask recipes by adding
14 BBMASK = "meta-xfce/recipes-multimedia"
16 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-xfce][kirkstone]' in th…
19 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-xfce][ki…
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/ |
| H A D | README | 1 meta-oe
6 URI: git://github.com/openembedded/openembedded-core.git
10 e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
14 pacman -S lib32-gcc-libs lib32-glibc
17 sudo apt-get install gcc-multilib linux-libc-dev:i386
19 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][kirkstone]' in the …
22 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][kir…
24 You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
27 Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well,
|
| /OK3568_Linux_fs/yocto/poky/documentation/toaster-manual/ |
| H A D | reference.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 some useful ``manage.py`` commands that are Toaster-specific.
26 OpenEmbedded Layer Index. A public instance of this layer index exists
28 layer index's web application at :yocto_git:`/layerindex-web/`.
40 developers. In fact, Toaster comes pre-configured with the OpenEmbedded
49 -----------------------------------
53 index in a manner similar to the way Toaster ties into the OpenEmbedded
67 ":ref:`overview-manual/yp-intro:the yocto project layer model`"
69 to create layers, see the ":ref:`dev-manual/common-tasks:understanding and creating layers`"
82 In the previous section, the code for the OpenEmbedded Metadata Index
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-webserver/ |
| H A D | README | 1 meta-webserver
4 This layer provides support for building web servers, web-based
10 ------------
14 URI: git://git.openembedded.org/openembedded-core
18 For some recipes, the meta-oe layer is required:
20 URI: git://git.openembedded.org/meta-openembedded
21 subdirectory: meta-oe
27 ------
29 recipes-httpd/ Web servers
30 recipes-php/ PHP applications
[all …]
|