linux/poky.git/meta/recipes-support/boost/boost.inc, branch yocto-3.3.2

recipes-support: Add missing HOMEPAGE and DESCRIPTION for recipes

2021-03-02T20:39:36+00:00

Fixes: [YOCTO #13471] (From OE-Core rev: 6db24928d62aeb093a0e6da6619713eaca57a96f) Signed-off-by: Ida Delphine Signed-off-by: Richard Purdie

native: Stop clearing PACKAGES

2021-01-29T21:21:53+00:00

Native recipes have been special and they don't have packages generated from them. The RDEPENDS/RPROVIDES and other runtime package specific variables can contain important data about dependencies recipes need though and currently it is required to write this information explicitly in the native case. We now delete the packaging tasks for native recipes which removes the need to clear PACKAGES. The next step to improve the metadata is to stop clearing it and ensure any entries in these variables are remapped appropriately. The R* variables were already being processed by the class extension code but the implementation was suboptimal. This patch stops clearing PACKAGES and PACKAGES_DYNAMIC and fixes the places where that caused issues in OE-Core, for example PACKAGES additions in anonymous python without the "-native" suffix and a case where the included classes caused a self reference in DEPENDS which would once have been removed by the previous code. The implementation uses datastore/parser parameters to ensure that the variable overrides are not overwritten when calling setVar which is appropriate for a function as close to the core as this one is. Some now unneeded code in python3-setuptools is dropped, there are further changes like this which can follow. This change was verified with OE-Core by comparing task-depends.dot generated by "bitbake world -g" before and after the change, the files were identical. (From OE-Core rev: fd6a007efa7cb45101a66f294af81d9d33bb3fab) Signed-off-by: Richard Purdie

boost: consolidate and update library list

2020-10-08T09:22:10+00:00

Add some new libraries to the list (fiber, headers, type_erasure). Move context/coroutine to the list instead of using overrides as it builds everywhere I can test it. Remove the mips16e override for wave as Boost fails so dramatically with mips16e enabled that this isn't even close to a fix. Someone who cares can fix this properly. (From OE-Core rev: 092228f2df6869e31b157ea08766b3e94bee6e29) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boost: don't specify gcc version

2020-10-08T09:22:10+00:00

There's no need to specify an ancient GCC version here as Boost will probe it. (From OE-Core rev: 2339bf5b0aceb8e55f4b38e44b2383389e514393) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boost: build a standalone boost.build

2020-10-08T09:22:10+00:00

Boost is a huge unirepo made from multiple submodules. To bootstrap it we need boost.build (previously bjam) which is also available as a solo repository. This smaller repository can unpack/build/package faster than the Boost unirepo can unpack. Rename the recipe to the current name of Boost.Build that installs a b2 binary, use the solo repository, and update the Boost recipe to use the b2 binary instead of bjam. (From OE-Core rev: 76079f921e596125b0e281ca95e2394d7688aaf2) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boost: move the build directory outside of S

2020-09-30T14:01:51+00:00

Instead of manually creating and deleting build directories, follow the idioms by setting B to WORKDIR/build, setting do_configure[cleandirs], and using ${B} where appropriate. (From OE-Core rev: 6ee1b1e6d65214ab32030ee4b37997f8a9871f25) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

multilib/recipes: Use new RecipePostKeyExpansion event

2020-05-27T09:47:05+00:00

There are issues with multilib due to the ordering of events where some functions see the remapped multilib dependencies and some do not. A significant problem is that the multilib class needs to make some changes before key expansion and some afterwards but by using existing event handlers, some code sees things in a partially translated state, leading to bugs. This patch changes things to use a new event handler from bitbake which makes the ordering of the changes explcit. The challenge in doing this is that it breaks some existing anonymous python and dyanmic assignments. In some cases these used to be translated and no longer are, meaning MLPREFIX has to be added. In some cases these are now translated and the MLPREFIX can be removed. This change does now make it very clear when MLPREFIX is required and when it is not, its just the migration path which is harder. The patch changes the small number of cases where fixes are needed. In particular, where a variable like RDEPENDS is conditionally extended (e.g. with an override), MLPREFIX is now required. This patch also reverts: base: Revert 'base.bbclass: considering multilib when setting LICENSE_EXCLUSION' This reverts 6597130256a1609c3e05ec5891aceaf549c37985 as the changes to multilib datastore handling mean its no longer necessary. (From OE-Core rev: b3fda056a674889cd9697e779de023d4f993d3ce) Signed-off-by: Richard Purdie

boost: fix reproducibilty issues

2020-03-12T22:49:28+00:00

fix cmake file references of image dir path (From OE-Core rev: e12caa834bef6b5d0cad7e96f79374a0dbf86aea) Signed-off-by: Jeremy A. Puhlman Signed-off-by: Richard Purdie

boost: update to 1.71.0

2019-08-28T10:31:21+00:00

Some notes: - bjam bootstrap scripts were changed, and the patch for that had to be adjusted. tools/build/src/engine/build.sh now supports an --debug option which the bjam-native recipe can use to get the debug build of b2. - a related patch was added to address a speed regression with the debug version of bjam - gcc.jam patch had to be refreshed because boost added more "cpu-flags" lines. - since 1.70.0, boost includes new cmake config files which are packaged in ${PN}-dev now so they make it into the SDK. (although 1.71.0 is needed to fix some bugs in them) (From OE-Core rev: 810aded01fc2ae2c27c2573135c20947453e50c6) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

boost: Fix build and enable context and coroutines on aarch64

2019-08-13T08:37:36+00:00

Like for ARM bjam need some hints about the ABI to properly build on aarch64. While at it also enable context and coroutine as these are supported on aarch64. (From OE-Core rev: 5140e0a64aac8c621fe0d839dea41b7b43a96b4d) Signed-off-by: Alban Bedel Signed-off-by: Richard Purdie