path: root/meta-skeleton
AgeCommit message (Collapse)Author
2020-10-26baremetal-helloworld: Fix install path since S doesnt have a trailing slashAlejandro Hernandez Samaniego
(From OE-Core rev: f099a4ec8e722f590fbf9b5ae87bb6ec29a5e6e6) Signed-off-by: Alejandro Enedino Hernandez Samaniego <> Signed-off-by: Richard Purdie <>
2020-10-10skeleton/baremetal-helloworld: Fix trailing slashRichard Purdie
This fixes a warning about a trailing slash on ${S}. (From OE-Core rev: 0685dac31a7ae614d9f75cd51b59c45dd050f52e) Signed-off-by: Richard Purdie <>
2020-07-08baremetal-helloworld: Use baremetal-image class to deploy the applicationAlejandro Hernandez
(From OE-Core rev: dd5a64feb5426ec870cf5d53ef056b24eb450487) Signed-off-by: Alejandro Hernandez Samaniego <> Signed-off-by: Richard Purdie <>
2020-07-03baremetal-helloworld: Use do_image_complete instead of do_deployAlejandro Hernandez
To better align with upstream and mimic how images are built, use do_image and do_image_complete instead of do_deploy to populate artifacts on DEPLOY_DIR_IMAGE. (From OE-Core rev: 9edb08c31700a85ce87344829989c1069d2760ab) Signed-off-by: Alejandro Hernandez Samaniego <> Signed-off-by: Richard Purdie <>
2020-05-18layer.conf: Move to gatesgarth namingRichard Purdie
We're still compatible with dunfell from the core perspective so that is left for compatibility (probably for the next week or two). (From OE-Core rev: 1e79324f8290b820fee034b0d4a8c353027879da) Signed-off-by: Richard Purdie <>
2020-04-29baremetal-helloworld: Fix IMGDEPLOYDIR expansionAlejandro Hernandez
IMGDEPLOYDIR is not being expanded anymore, this causes do_rootfs to fail because it can't create the manifest file, we can set it to the default being set on image.bbclass since this is only a decoy function anyway to satisfy testimage, this makes do_rootfs happy and allows it to continue. (From OE-Core rev: 06ed491e30b47b8c5f89746e890519dd7de800fd) Signed-off-by: Alejandro Hernandez Samaniego <> Signed-off-by: Alejandro Hernandez Samaniego <> Signed-off-by: Richard Purdie <>
2020-03-15layer.conf: Update to LAYERSERIES_CORENAME to dunfellRichard Purdie
Update the layer core name to the new release name. (From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e) Signed-off-by: Richard Purdie <>
2020-02-05baremetal-helloworld: Create recipe for baremetal examples on QEMUAlejandro Enedino Hernandez Samaniego
Create HelloWorld examples that run on several of the QEMU architectures supported by the build system. This recipe can be used by anyone to understand how baremetal applications can be built using OpenEmbedded and how the wiring to set them up could be. This should also facilitate creating/extending the OE testing infrastructure to allow baremetal applications or RTOSs to be tested in the same way that Linux currently is. This can easily be extended to work on other MACHINES in the future. To run this example: $ source oe-init-buildenv $ bitbake-layers add-layer ../meta-skeleton # TCLIBC="baremetal" would work as well $ echo "TCLIBC = \"newlib\"" >> ./conf/local.conf $ echo "MACHINE = \"qemuarm64\"" >> ./conf/local.conf $ bitbake baremetal-helloworld $ runqemu runqemu - INFO - Running bitbake -e ... runqemu - INFO - Continuing with the following parameters: KERNEL: [tmp/deploy/images/qemuarm64/baremetal-helloworld-qemuarm64.bin] MACHINE: [qemuarm64] FSTYPE: [bin] ROOTFS: [tmp/deploy/images/qemuarm64/baremetal-helloworld-qemuarm64.bin] CONFFILE: [tmp/deploy/images/qemuarm64/baremetal-helloworld-qemuarm64.qemuboot.conf] Hello OpenEmbedded! (From OE-Core rev: b314e9a0923c8aa95a2f2c3f48d956206e9885a7) Signed-off-by: Alejandro Enedino Hernandez Samaniego <> Signed-off-by: Richard Purdie <>
2019-10-08layer.conf: Update for zeus seriesRichard Purdie
(From OE-Core rev: a5c9709b8da6e7ad62167b5036e7f454a62aa83e) Signed-off-by: Richard Purdie <>
2019-05-09meta/lib+scripts: Convert to SPDX license headersRichard Purdie
This adds SPDX license headers in place of the wide assortment of things currently in our script headers. We default to GPL-2.0-only except for the oeqa code where it was clearly submitted and marked as MIT on the most part or some scripts which had the "or later" GPL versioning. The patch also drops other obsolete bits of file headers where they were encoountered such as editor modelines, obsolete maintainer information or the phrase "All rights reserved" which is now obsolete and not required in copyright headers (in this case its actually confusing for licensing as all rights were not reserved). More work is needed for OE-Core but this takes care of the bulk of the scripts and meta/lib directories. The top level LICENSE files are tweaked to match the new structure and the SPDX naming. (From OE-Core rev: f8c9c511b5f1b7dbd45b77f345cb6c048ae6763e) Signed-off-by: Richard Purdie <>
2019-04-02layer.conf: Update to warrior release name seriesRichard Purdie
(From OE-Core rev: 13e45fffb66c7cb7ba0d07bed063c0c5ce57004b) Signed-off-by: Richard Purdie <>
2018-09-25meta-skeleton/meta-selftest: Update to thudRichard Purdie
(From OE-Core rev: 4c48e59c58e62d70b900c4356953f5b66fba2353) Signed-off-by: Richard Purdie <> add RPROVIDESJuro Bystricky
Although the package will get an automatic prefix "kernel-module", so the package kernel-module-hello does exist, populating rootfs can generate an error: - nothing provides kernel-module-hello ... This is quite unfortunate, as this recipe is used as a sample. Adding RPROVIDES_${PN} += "kernel-module-hello" to the recipe fixes the problem. [YOCTO #12641] (From OE-Core rev: ca17a7bbea5f5454da43545d544ff7772d83ac19) Signed-off-by: Juro Bystricky <> Signed-off-by: Richard Purdie <>
2018-04-06layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie
Also set LAYERSERIES_COMPAT for core (we're compatible with ourself). (From OE-Core rev: 4aa43cd844781a07a2dbf17f21ed35c6a0100d02) Signed-off-by: Richard Purdie <>
2017-06-12meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.confRichard Purdie
This means mismatched layers are more clearly identified to the user in cases where compatibility has not been tested. This is perhaps not as needed for the core repository (other than CORENAMES) but lets lead by example. (From OE-Core rev: cde66d5eac8e5c2821ba225dc4be4af4e0581652) Signed-off-by: Richard Purdie <>
2017-01-09useradd-example: exclude from worldKai Kang
(From OE-Core rev: 1e03ad25d8b9536d5e7f9969809a4df01e55fe3a) Signed-off-by: Kai Kang <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2016-10-28Remove $COREBASE/LICENSE from LIC_FILES_CHKSUMOlaf Mandel
Several recipes reference the LICENSE file in their LIC_FILES_CHKSUM variable as ${COREBASE}/LICENSE. This forces distribution providers to keep this file verbatim or to overload the affected recipes. The section "Moving to the Yocto Project 1.6 Release" in the Yocto manual suggests removing the LICENSE file where possible. Remove LICENSE in cases where COPYING.MIT is also given and replace LICENSE with COPYING.MIT if the former was the only entry. All modified recipes specify LICENSE = "MIT" and none of the in-tree files specify a different license either. As the packages do not change (the license files are not contained in them), do not increase PR. (From OE-Core rev: 0059e0661826c857a07c862bcb46162671e0e330) Signed-off-by: Olaf Mandel <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2016-07-08service: obey CFLAGS, LDFLAGSChristopher Larson
(From OE-Core rev: 8a227125991951c1ddd44bec0b6243474ebc363a) Signed-off-by: Christopher Larson <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-10-19linux-yocto-custom: fix typo in Upstream-Status tagRoss Burton
(From OE-Core rev: cb46e70148c4210071299acc648c10f1c87cd3fd) Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-10-01linux-yocto-custom: Update for newer kernelSaul Wold
Update the NAME version tweak example patch for the newer kernel. This moves the example to the 4.2 stable kernel and appends -custom to the VERSION string. (From OE-Core rev: dc26472661bdc0ed4248d7ab462a296f3c86c421) Signed-off-by: Saul Wold <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-08-24service: tweak example recipePaul Eggleton
* Drop PR = "r0" * Reorder lines so that packaging definitions are at the end (From OE-Core rev: e6cf787871518119205c7d764f5478fd853e2576) Signed-off-by: Paul Eggleton <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-08-24hello-mod: drop PV and PRPaul Eggleton
* PR = "r0" is the default, no need to set it (and most people won't need to set it anyway with the PR service) * PV = "0.1" is already set by virtue of 0.1 being in the filename (From OE-Core rev: 91b323526427f67a8982c7b090e505aaf810d4e7) Signed-off-by: Paul Eggleton <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-05-24linux-yocto-custom: clarify bbappend versus copy in commentsBruce Ashfield
The kernel development manual recommends making a copy of linux-yocto-custom, while the comments in the recipe talk about bbappends. To synchronize the two, we remove the bbappend references from the recipe and instead indicate that a copy should be updated. [YOCTO: #6925] (From OE-Core rev: 121498714b03339d2e5090c2a8fe0618bbaa8610) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2015-03-25skeleton: clarify linux-yocto-custom workflowBruce Ashfield
It was pointed out that the kernel development documentation recommends making a copy of linux-yocto-custom, while the comments in the recipe itself suggest a bbappend. To keep things consistent between these two sources, we update the comment in the recipe itself to also recommend a copy (and rename). [YOCTO: #6925] (From OE-Core rev: aabd47e46a31b526ee880dfd22a1a1f2831ab355) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2014-05-06linux-yocto-custom: provide defconfig guidanceBruce Ashfield
As reported by Andrea, defconfigs created with savedefconfig should specify their expansion mode as "--alldefconfig' for custom yocto recipes. To ensure that this is documented, we can add a comment in the skeleton recipe. Reported-by: Andrea Adami <> (From OE-Core rev: 2c41a28c9a9772531dcfc7079604ff2441c71f8f) Signed-off-by: Bruce Ashfield <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2014-03-27meta-skeleton: Add name attribute to SRC_URIJukka Rissanen
The SRCREV_machine line does not work without having name=machine attribute in SRC_URI. This error is seen if the custom kernel recipe is used without the name attribute: NOTE: Error during finalise of .../ ERROR: ExpansionError during parsing .../ Failure expanding variable do_patch: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure for URL: 'git://;protocol=git;nocheckout=1'. Please set a valid SRCREV for url ['SRCREV_default_pn-linux-yocto-custom', 'SRCREV_default', 'SRCREV_pn-linux-yocto-custom', 'SRCREV'] (possible key names are git://;protocol=git;nocheckout=1, or use a ;rev=X URL parameter) (From OE-Core rev: 760ae021fe1714d04c34bc00d472e2d756b3823a) Signed-off-by: Jukka Rissanen <> Signed-off-by: Richard Purdie <>
2014-03-17linux-yocto-custom: Use SRCREV_machineDarren Hart
The Yocto kernel tools look for SRCREV_machine in do_validate_branches, if it's empty, it just returns and silently continues. This likely needs at least a warning. However, this recipe should be using SRCREV_machine, and not just SRCREV. (From OE-Core rev: f36de92551c8c44a15f1997e65cd8ee957143d95) Signed-off-by: Darren Hart <> Reported-by: Saul Wold <> Cc: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2014-02-20recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues (part 2)Matthieu Crapet
Completes previous commit b5292d4115a4555a66b5e35acdc67dd71fb8577f. Updates SUMMARY[doc] (meta/conf/documentation.conf). Changes: - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR (From OE-Core rev: ad17dfd31a2b97b3e610a0ea0889f5ecb2a63b97) Signed-off-by: Matthieu Crapet <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2014-02-02meta-skeleton: rename busybox's bbappend fileChen Qi
As busybox has been upgraded, rename this bbappend file to make it match the current version of busybox. (From OE-Core rev: 12e33bd0dc02720122eb8088b08a181b13b6ef0e) Signed-off-by: Chen Qi <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2014-01-02Update after toplevel LICENSE file checksum changeRichard Purdie
(From OE-Core rev: bbd88aebcabbb19c27a7d752d4a5b8ad9ff9412e) Signed-off-by: Richard Purdie <>
2014-01-02Fix license notices for OE-CorePaul Eggleton
* Fix up LICENSE: - Replace reference to Poky with OpenEmbedded - Remove reference to bitbake and meta-extras that aren't part of this repository - Clarify license statements * Add a COPYING.GPLv2 file in meta/ for the GPLv2 parts * Add a COPYING.MIT file to meta-skeleton consistent with the other meta-* directories (From OE-Core rev: b777180f317a844513fcaae42fd7c91dff308f9b) Signed-off-by: Paul Eggleton <> Signed-off-by: Richard Purdie <>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. (From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292) Signed-off-by: Paul Eggleton <> Signed-off-by: Richard Purdie <>
2013-12-14useradd-example: add example for setting clear text passwordChen Qi
Use '-P' option for user3 to set a clear text password. This is supposed to serve as an example of how to set clear text password in recipes. (From OE-Core rev: 6f47698e1ef8103cade8b954825848bb8986158c) Signed-off-by: Chen Qi <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-08-20hello-mod: Add comment for kernel module package namingYang Shi
modules bbclass renames kernel module packages with "kernel-module-" prefix automatically. (From OE-Core rev: 6640f312062ad6648459f0b75086e9a8614300a9) Signed-off-by: Yang Shi <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-08-20Revert "hello-mod: Ensure the produced package name begins with kernel-module-"Yang Shi
[YOCTO #4286] The package runtime mapping rename issue is already fixed by commit 0bc564af07c1bae8112f834a60aea3b72af7de13, the "kernel-module-" workaround is not necessary anymore for out-of-tree module package, so revert that commit. This reverts commit 71aafc214fe407b7620e747c11dfb8326c867b1c. (From OE-Core rev: b0676d2ffceec3027aee8d2d450ae6318085341e) Signed-off-by: Yang Shi <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-08-16meta-skeleton: layer.conf Should also have .bbappend in exampleSaul Wold
This will allow for an example recipe with a .bbappend, such as busybox or kernel configure fragments. (From OE-Core rev: 2a2a2540b37880cdd866f01d8e4077cbd0378749) Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-08-13meta-skeleton: Add busybox config fragment exampleSaul Wold
This shows an example of the config fragment support that both the linux-yocto and busybox recipes use. This example is specific to busybox. By adding busybox CONFIG options into a .cfg file and then adding that .cfg file to SRC_URI the script will correctly handle these CONFIG options during the do_configure task. The script uses a last-in wins method. For more details about this, see the Kernel Development Manual Section 2.2.3 (From OE-Core rev: 57662d4f813d5795cac1529633db80a09efdb089) Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-04-13hello-mod: Ensure the produced package name begins with kernel-module-Mark Hatle
The special key kernel-module- is necessary for the system to avoid a package rename when installing a multilib image. For example: local.conf: IMAGE_INSTALL_append = " hello-mod" bitbake lib32-core-image-minimal The system will translate names and prepend 'lib32-', unless the package begins with kernel-module-. (From OE-Core rev: b847f87f4213db917d6760cd399c0afae996cf23) Signed-off-by: Mark Hatle <> Signed-off-by: Richard Purdie <>
2013-04-10meta-*/conf/layer.conf: tweak BBFILES commentPaul Eggleton
"packages" was the old name (pre-2010) under which the recipe files were stored. (From OE-Core rev: c71fa87bc2e7155e69ea5ff7a284a05073602eed) Signed-off-by: Paul Eggleton <> Signed-off-by: Richard Purdie <>
2013-03-20core-image-multilib-example: Location of changedMark Hatle
(From OE-Core rev: 6aacf7b2c571bf1004caaa9883e58c1f22e37fec) Signed-off-by: Mark Hatle <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-03-19layer.conf: avoid unnecessary early expansion with :=Christopher Larson
bitbake handles immediate expansions of LAYERDIR for us automatically. (From OE-Core rev: 643ac87145eba5dc105377041bc3deb163b62926) Signed-off-by: Christopher Larson <> Signed-off-by: Richard Purdie <>
2013-03-18layer.conf: Add LAYERVERSION and
Add LAYERVERSION and LAYERDEPENDS to following oe-core layers: meta-hob, meta-skeleton (From OE-Core rev: 8d868a9b64b460aa38462115bbb17634544c71cc) Signed-off-by: Wenzong Fan <> Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2013-02-25meta-skeleton: Add example multilib usagesRichard Purdie
(From OE-Core rev: 514b0ab066bebd52980467e935c0e5df9e480db4) Signed-off-by: Richard Purdie <> Signed-off-by: Constantin Musca <> Signed-off-by: Richard Purdie <>
2012-10-03linux-yocto-custom: Clarify defconfig usageDarren Hart
It is necessary to supply file://defconfig to the SRC_URI when using a defconfig (it is not implicitly understood as the commentary might currently suggest). (From OE-Core rev: 3e244e0e9c10438c2236e56b3de664d4560791f0) Signed-off-by: Darren Hart <> CC: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2012-08-07linux-yocto-custom: Clarify usage and clear COMPATIBLE_MACHINEDarren Hart
There has been some confusion over proper use of the linux-yocto-custom recipe. It is not intended to build as is from meta-skeleton. It should be modified via a bbappend file to provide a Linux kernel config at the very least. Update the commentary to make this requirement more explicit. Add some additional detail about how to create a bbappend file and how and when to modify the various variables. Clear COMPATIBLE_MACHINE so bitbake will not attempt to build the recipe unless the user explicitly adds there machine to the variable, which should encourage them to read the recipe comments before attempting to build it. (From OE-Core rev: 8ac3d0566e793777ec4f6629ef752d6db6231ca9) Signed-off-by: Darren Hart <> CC: Bruce Ashfield <> CC: Tom Zanussi <> Signed-off-by: Darren Hart <> Signed-off-by: Richard Purdie <>
2012-08-06useradd-example: use ${datadir} instead of /usr/share for packagingJavier Martinez Canillas
It is considered good practice to use the build system provided variables instead of directly specify hardcoded paths. (From OE-Core rev: b93a9dadc9a2754d4e33929bda8dba46dd20b694) Signed-off-by: Javier Martinez Canillas <> Signed-off-by: Richard Purdie <>
2012-07-03linux-yocto-custom: Remove linux-toolsDarren Hart
Remove the linux-tools include as perf is now packaged independently. Without this, including meta-skeleton in bblayers.conf results in a build failure as cannot be found. (From OE-Core rev: 9d27daeafcc6ea892dee0ee5d0816069b04f6771) Signed-off-by: Darren Hart <> Acked-by: Bruce Ashfield <> CC: Tom Zanussi <> Signed-off-by: Richard Purdie <>
2012-06-18meta-skeleton: add linux-yocto-custom reference recipeBruce Ashfield
Adding a skeleton/refrence recipe for using a subset of the yocto kernel tools against kernel git repositories. Sample/reference configuration fragments, features and a patch are provided and documented in the recipe. From the recipe itself: Provides an example/minimal kernel recipe that uses the linux-yocto and oe-core kernel classes to apply a subset of yocto kernel management to git managed kernel repositories. Notes: kconfig(s): the kernel must be configured with a defconfig, or via configuration fragment(s). Either of these can be added via bbappend. patches: patches can be merged into to the source git tree itself, added using standard bbappend syntax or controlled via .scc feature descriptions (also via bbappends) example configuration addition: SRC_URI += "file://smp.cfg" example patch addition (for kernel v3.4 only): SRC_URI += "file://0001-linux-version-tweak.patch example feature addition (for kernel v3.4 only): SRC_URI += "file://feature.scc" Warning: Building the sample kernel tree ( without providing any configuration will result in build or boot errors. This is not a bug it is a required element for creating a valid kernel. [YOCTO #2397] (From OE-Core rev: 4b6f29ddb00480896f47d96ea376f3a6f6d8451e) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
2012-04-10hello-mod: Move hello-mod from meta to meta-skeletonDarren Hart
Fixes [YOCTO #1501] hello-mod is an example kernel module, and does not provide any real functionality. As such, it would be better placed under meta-skeleton than meta. (From OE-Core rev: bde1744018afd4616e114b20ffdc21b9abddcedc) Signed-off-by: Darren Hart <> Signed-off-by: Richard Purdie <> update example documentation commentsScott Garman
Clarify that only packages listed in USERADD_PACKAGES will include the user/group creation code. (From OE-Core rev: 70aaac37968bf2b35d6a536c3f3f69fe3620255c) Signed-off-by: Scott Garman <> Signed-off-by: Richard Purdie <>