| /openbmc/openbmc/poky/scripts/ |
| H A D | yocto-check-layer | 101 layers = detect_layers(args.layers, args.no_auto) 102 if not layers: 111 dep_layers = dep_layers + layers 113 dep_layers = layers 127 for layer in layers: 132 layers.remove(layer) 136 layers.remove(layer) 140 if not layers: 146 for layer in layers: 154 if d not in layers: [all …]
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | yocto-project-compatible.rst | 11 After the introduction of layers to OpenEmbedded, it quickly became clear 12 that while some layers were popular and worked well, others developed a 13 reputation for being "problematic". Those were layers which didn't 16 because such layers are often created by developers with a particular focus 21 As a result of noticing such patterns and friction between layers, the project 22 developed the "Yocto Project Compatible" badge program, allowing layers 25 questions where layers can declare if they meet the appropriate criteria. 30 See :ref:`dev-manual/layers:making sure your layer is compatible with yocto project` 42 Over time, the project identified characteristics in layers that allow them 43 to operate well together. "anti-patterns" were also found, preventing layers [all …]
|
| /openbmc/openbmc/poky/scripts/lib/checklayer/ |
| H A D | __init__.py | 130 layers = [] 142 layers.append(layer) 150 layers.append(layer) 152 return layers 154 def _find_layer(depend, layers): argument 155 for layer in layers: 164 def sanity_check_layers(layers, logger): argument 175 for layer in layers: 185 def get_layer_dependencies(layer, layers, logger): argument 186 def recurse_dependencies(depends, layer, layers, logger, ret = []): argument [all …]
|
| /openbmc/openbmc/poky/meta/lib/bblayers/templates/ |
| H A D | example.bb | 1 SUMMARY = "bitbake-layers recipe" 2 DESCRIPTION = "Recipe created by bitbake-layers" 8 bb.plain("* Example recipe created by bitbake-layers *");
|
| /openbmc/openbmc/poky/meta/lib/bblayers/ |
| H A D | buildconf.py | 61 layers = oe.buildcfg.get_layer_revisions(self.tinfoil.config_data) 65 for l in layers: 72 …ne of the currently enabled layers:\n{}".format(args.layerpath, "\n".join([l[0] for l in layers]))) 74 …ed-core not in one of the currently enabled layers:\n{}".format("\n".join([l[0] for l in layers]))) 76 relpaths_to_oecore = [(l[0], os.path.relpath(l[0], start=oecore)) for l in layers]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/ |
| H A D | typeaheads.py | 22 layers = prj.get_all_compatible_layer_versions() 23 layers = layers.order_by('layer__name') 30 layers = layers.exclude( 33 primary_results = layers.filter(layer__name__istartswith=search_term) 34 secondary_results = layers.filter(
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | layers.rst | 7 :term:`Metadata` into multiple layers. 19 It is very easy to create your own layers to use with the OpenEmbedded 21 layers. This section describes the steps you perform by hand to create 22 layers so that you can better understand them. For information about the 24 ":ref:`bsp-guide/bsp:creating a new bsp layer using the \`\`bitbake-layers\`\` script`" 26 …Guide and the ":ref:`dev-manual/layers:creating a general layer using the \`\`bitbake-layers\`\` s… 34 for a list of layers from the OpenEmbedded community that can be used in 113 layers. 123 Lists all layers on which this layer depends (if any). 135 ``.bbappend``. Generally, developers create layers using [all …]
|
| H A D | custom-distribution.rst | 30 ":ref:`dev-manual/layers:creating a general layer using the \`\`bitbake-layers\`\` script`" 101 ":ref:`dev-manual/layers:creating your own layer`" and 102 ":ref:`dev-manual/layers:following best practices when creating layers`" 114 ":ref:`dev-manual/layers:appending other layers metadata with your layer`"
|
| /openbmc/openbmc/poky/scripts/contrib/ |
| H A D | patchreview.py | 225 def gather_patches(layers): argument 227 for directory in layers: 232 def count_recipes(layers): argument 234 for directory in layers: 248 layers = find_layers(args.directory) variable 250 patches = gather_patches(layers) 265 row['recipe_count'] = count_recipes(layers)
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 20 You will be finding layers with recipes and other metadata that support these 32 </software-overview/layers/>` or even the :oe_layerindex:`OpenEmbedded 44 layers to that. Here is the information :ref:`about adding layers 45 <dev-manual/layers:Understanding and Creating Layers>`. 47 #. **Based on the layers you've chosen, make needed changes in your 57 Use the ``bitbake-layers create-layer`` tool for Yocto Project 2.4+ 59 ``yocto-layer create`` tool. The ``bitbake-layers`` tool also provides a number 61 :ref:`dev-manual/layers:creating a general layer using the 62 \`\`bitbake-layers\`\` script` section. 68 bsp layer using the \`\`bitbake-layers\`\` script>`. For example, given a [all …]
|
| /openbmc/openbmc/meta-openembedded/ |
| H A D | README.md | 1 Collection of layers for the OE-core universe 5 This repository is a collection of layers to suppliment OE-Core
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | check-machine-coverage | 14 layers = (p.name for p in metaarm.glob("meta-*") if p.is_dir()) variable 16 machines = list_machines(layers)
|
| H A D | listmachines.py | 10 def list_machines(layers: typing.Sequence[str]) -> typing.Set[str]: 18 for layer in layers:
|
| /openbmc/openbmc/poky/meta/lib/oe/ |
| H A D | copy_buildsystem.py | 46 layers = list(self.layerdirs) 49 layers.append(corebase) 53 layers.append(os.path.join(corebase, 'meta-skeleton')) 57 if layer_exclude in layers: 59 layers.remove(layer_exclude) 62 layers_cp = layers[:] 67 layers.remove(layer) 71 layernames = [os.path.basename(layer) for layer in layers] 83 for layer in layers:
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/bldcontrol/ |
| H A D | localhostbecontroller.py | 82 def setLayers(self, bitbake, layers, targets): argument 105 for layer in layers: 219 for layer in layers: 235 customrecipe, layers) 252 def setup_custom_image_recipe(self, customrecipe, layers): argument 272 br_layer_base_recipe = layers.get( 318 def triggerBuild(self, bitbake, layers, variables, targets, brbe): argument 319 layers = self.setLayers(bitbake, layers, targets) 352 'BBLAYERS = "%s"' % ' '.join(layers)) 383 for layer in layers:
|
| /openbmc/openbmc/meta-amd/ |
| H A D | README.md | 2 The meta-amd project consists of collection of BSP and distro layers for AMD customer reference ser… 11 conf, classes, and recipes-*, for description of the BSP layers consult the
|
| /openbmc/openbmc/poky/meta/recipes-graphics/vulkan/ |
| H A D | vulkan-validation-layers_1.4.313.0.bb | 1 SUMMARY = "Vulkan Validation layers" 2 DESCRIPTION = "Khronos official Vulkan validation layers to assist developers \ 45 # vulkan-validation-layers, spirv-headers, spirv-tools,
|
| /openbmc/openbmc/poky/bitbake/lib/bblayers/ |
| H A D | action.py | 126 layers = self.bblayers 131 for layerdir in layers: 141 layers = found_layerdirs 147 for layerdir in layers: 153 for layer in layers: 218 layerdir = layers[0]
|
| /openbmc/openbmc/poky/documentation/brief-yoctoprojectqs/ |
| H A D | index.rst | 202 layers into your configuration please add entries to conf/bblayers.conf. 227 - 'bitbake-layers' handles common layer tasks 302 In general, layers are repositories that contain related sets of 304 Isolating related metadata into functionally specific layers facilitates 313 #. **Find a Layer:** Many hardware layers are available. The Yocto Project 314 :yocto_git:`Source Repositories <>` has many hardware layers. 335 next to other layers inside the Poky reference repository on your build 341 It is recommended for layers to have a branch per Yocto Project release. 361 Use the ``bitbake-layers add-layer`` command to add the layer to the 367 $ bitbake-layers add-layer ../meta-altera [all …]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/tests/ |
| H A D | test.js | 50 assert.ok(prjInfo.layers.length > 0); 89 var origNumLayers = prjInfo.layers.length; 94 assert.ok(prjInfo.layers.length > origNumLayers,
|
| /openbmc/openbmc/meta-openembedded/meta-python/ |
| H A D | README.md | 15 layers: meta 19 layers: meta-oe
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | reference.rst | 20 layers. In particular, we are concerned with layers that you can use 25 of custom layers. A good example of an existing layer index is the 32 API, store the information about the layers in the Toaster database, and 34 information and build layers from Toaster itself without having to 35 clone or edit the BitBake layers configuration file ``bblayers.conf``. 38 custom layers that need to be built on a regular basis by a community of 59 layers that developers build and access using the Yocto Project on a 60 regular basis. This set of layers needs to exist and you need to be 63 layers. 65 For general information on layers, see the [all …]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/ |
| H A D | projectpage.js | 41 updateProjectLayers(prjInfo.layers); 116 function updateProjectLayers(layers){ argument 119 if (layers.length === 0){ 124 for (var i in layers){ 125 var layerObj = layers[i];
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 53 Variables starting with ``LAYER`` configure how BitBake handles layers. 54 Additionally, variables starting with ``BB`` configure how layers and files are 57 - :term:`LAYERDEPENDS` is used to configure on which layers a given layer 60 - The configured layers are contained in :term:`BBLAYERS` and files in
|
| /openbmc/docs/ |
| H A D | meta-layer-guidelines.md | 10 ## Meta layers should not patch projects that exist within the openBMC tree 21 in code review. If patches are checked into meta layers, generally the 35 ## Meta layers should not patch Yocto recipes and projects 55 ## Meta layers should avoid using EXTRA_OEMAKE and EXTRA_OEMESON 74 ## Meta layers should not have recipes that point to proprietary licensed code 109 ## Meta layers should not point to OpenBMC specific repositories outside of <https://github.com/ope… 157 ## Meta-layers should not contain compiled code 166 Meta-layers are often set up where company-specific developers have merge 167 authority. Placing code into these meta-layers allows practices that do not
|