linux/poky.git/meta/recipes-extended/gperf, branch nanbield

gperf: Make the code C++17 compliant

2023-01-16T10:42:07+00:00

Fixes | ../../gperf-3.1/lib/getline.cc:58:7: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] | register int c = getc (stream); | ^~~~~~~~~ (From OE-Core rev: dd137feabdad2e7a2b3d107c703aad577a2e79c7) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

recipes: Enable nativesdk for gperf, unifdef, gi-docgen and its dependencies

2022-12-21T10:16:31+00:00

I'm building a SDK (bitbake task: populate_sdk) for WPE/WebKit development [1] and I need the tools below to be extended with the class nativesdk. They work fine on the SDK after this change. The needs are because: 1) gperf and unifdef are required by the WebKit build system at build time. 2) gi-docgen is required by the WebKit build system when CMake option 'ENABLE_DOCUMENTATION' is enabled, and gi-docgen itself depends on the following python modules that also need to enable nativesdk: python3-markdown, python3-smartypants and python3-typogrify [1] See: - https://github.com/Igalia/meta-webkit/pull/436 - https://bugs.webkit.org/show_bug.cgi?id=249604 (From OE-Core rev: 6cb38fd632a161bea7b9a04de400d8be8d565b07) Signed-off-by: Carlos Alberto Lopez Perez Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

gperf: Switch to upstream patch

2022-07-09T19:58:35+00:00

Upstream merged a patch to handle the reproducibility issue, switch to their patch which is functionally equivalent. (From OE-Core rev: db28cd0e1540e44db963108430205c8c0c817774) Signed-off-by: Richard Purdie

gperf: Add a patch to work around reproducibility issues

2022-07-04T21:51:49+00:00

Add a patch to avoid writing the full pathname to gperf into source files which leads to reproducibility issues. This fixes issues with systemd reproducibility in particular. (From OE-Core rev: dea3c7ee2a413f7dc5f13ec006592084f7fb266c) Signed-off-by: Richard Purdie

meta/meta-selftest/meta-skeleton: Update LICENSE variable to use SPDX license identifiers

2022-02-20T16:45:25+00:00

An automated conversion using scripts/contrib/convert-spdx-licenses.py to convert to use the standard SPDX license identifiers. Two recipes in meta-selftest were not converted as they're that way specifically for testing. A change in linux-firmware was also skipped and may need a more manual tweak. (From OE-Core rev: ceda3238cdbf1beb216ae9ddb242470d5dfc25e0) Signed-off-by: Richard Purdie

gperf: don't use aclocal.m4/acinclude.m4 dance

2017-12-10T22:45:19+00:00

gperf doesn't use aclocal so don't call aclocal. (From OE-Core rev: e080880a82df7f9402a76f20b74e0f43b87f5b71) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gperf: merge inc into bb

2017-12-10T22:45:19+00:00

(From OE-Core rev: 28b7ff06d685873aee54b6c27caab3e9518c004a) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gperf: upgrade to 3.1

2017-08-13T08:27:37+00:00

(From OE-Core rev: 9784d22fee75d5e2998e0d5f226f54ef812a019b) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

recipes: Move out stale GPLv2 versions to a seperate layer

2017-03-07T20:05:31+00:00

These are recipes where the upstream has moved to GPLv3 and these old versions are the last ones under the GPLv2 license. There are several reasons for making this move. There is a different quality of service with these recipes in that they don't get security fixes and upstream no longer care about them, in fact they're actively hostile against people using old versions. The recipes tend to need a different kind of maintenance to work with changes in the wider ecosystem and there needs to be isolation between changes made in the v3 versions and those in the v2 versions. There are probably better ways to handle a "non-GPLv3" system but right now having these in OE-Core makes them look like a first class citizen when I believe they have potential for a variety of undesireable issues. Moving them into a separate layer makes their different needs clearer, it also makes it clear how many of these there are. Some are probably not needed (e.g. mc), I also wonder whether some are useful (e.g. gmp) since most things that use them are GPLv3 only already. Someone could now more clearly see how to streamline the list of recipes here. I'm proposing we mmove to this separate layer for 2.3 with its future maintinership and testing to be determined in 2.4 and beyond. (From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b) Signed-off-by: Richard Purdie

recipes: Remove PR = r0 from all recipes

2013-10-30T14:52:04+00:00

Remove all PR = "r0" from all .bb files in oe-core. This was done with the command sed -e '/^PR.*=.*r0\"/d' recipes*/*/*.bb -i We've switching to the PR server, PR bumps are no longer needed and this saves people either accidentally bumping them or forgetting to remove the lines (r0 is the default anyway). (From OE-Core rev: 58ae94f1b06d0e6234413dbf9869bde85f154c85) Signed-off-by: Richard Purdie