Search results
From Yocto Project
Jump to navigationJump to search
- | Yocto Metadata Layers || || meta.watcher@fake.user2 KB (229 words) - 13:21, 21 December 2010
- * implements a new layer that contains generic/specific metadata used only by tests ...r testing and thus remove the need to modify the structure of the existing metadata or the need to create them at runtime.8 KB (1,202 words) - 06:48, 19 February 2024
- A complete set of Linux package versions is specified in the metadata for the project; these versions are known to work correctly together. A rob The Yocto Project shares the core build tool (BitBake) and metadata syntax with OpenEmbedded, particularly the core set of components known as17 KB (2,669 words) - 17:18, 4 May 2015
- === Metadata === Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through o10 KB (1,274 words) - 13:03, 2 July 2013
- ...y want to place your changes in the form of a patch to be applied from the metadata - devtool provides help with this as well. Commit your changes using "git c3 KB (576 words) - 16:47, 5 March 2024
- | Aiming for compatibility and interoperability among different metadata layers. || Y or N || bgcolor="" | (Delete if "Y") | Aiming for compatibility and interoperability among different metadata layers. || Y || bgcolor="" |14 KB (1,950 words) - 18:41, 19 June 2012
- * The metadata now requires to use Python 3 syntax. There are many Python 3 porting guides ...added allowing multiple versions of bitbake to work with suitably written metadata (which includes OpenEmbedded-Core / Poky). Anyone with custom bitbake task6 KB (874 words) - 13:54, 7 November 2016
- Our shared state (sstate) mechanism base our builds on hashes of input metadata, reusing the outputs if the inputs are the same.3 KB (537 words) - 14:05, 7 February 2017
- * Aim for compatibility and interoperability between different metadata layers.3 KB (462 words) - 17:18, 17 May 2012
- === Metadata === Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through o12 KB (1,615 words) - 15:20, 10 December 2013
- === Metadata === Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through o13 KB (1,704 words) - 15:10, 29 April 2014
- === Metadata === Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through o13 KB (1,706 words) - 13:55, 9 January 2015
- |Migrated BitBake and python functions in the OE metadata to Python 3 ...date with various upstream project, continue to work on the quality of the metadata and keeping up to date with bug fixing.7 KB (907 words) - 22:02, 20 April 2017
- ...eate the layers metadata inside testresults.json configuration. The layers metadata were important data required by the "resulttool store" for creating the git11 KB (1,443 words) - 04:50, 7 April 2020
- ...By forcing sstate cache to be used regardless of input changes, the recipe metadata will no longer directly reflect the output of a bitbake command. This featu4 KB (660 words) - 01:51, 12 April 2017
- ...yoctoproject.org/training/kernel-lab. It has a pdf, and supporting layers/metadata to allow you to follow along. There is also a kernel development manual lo5 KB (856 words) - 01:49, 1 November 2016
- Currently, [[oe-selftest]] covers all [[#Bitbake]], oe-core and [[#Metadata]] autoamted tests. ==== Metadata ====24 KB (3,325 words) - 15:39, 29 March 2016
- * OE-Core: the metadata and glue which binds the system together: how to build software, how to sep3 KB (522 words) - 16:53, 14 October 2016
- The meta-intel repository consists of a set of BSPs and some common metadata. Because those BSPs each have separate owners, we can't make a blanket ass5 KB (861 words) - 09:27, 20 July 2018
- ...perform on Yocto Project using kernel tools, and shows you how to use the metadata required to work with the kernel.4 KB (556 words) - 21:35, 6 November 2017