linux/poky.git/meta/recipes-support/boost, branch master-next

boost: upgrade 1.88.0 -> 1.89.0

2025-09-08T17:02:39+00:00

Changelog: https://www.boost.org/releases/1.89.0/ (From OE-Core rev: 67ed4255dfa70b7b1d6b32e60a436bad67051d52) Signed-off-by: Gyorgy Sarvari Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

boost-build-native: upgrade 1.87 -> 1.89

2025-09-08T17:02:39+00:00

Changelog: https://www.boost.org/releases/1.89.0/ (From OE-Core rev: d1a1dedc92f90901998a8dec31450bb219c58c0a) Signed-off-by: Gyorgy Sarvari Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove consecutive blank lines

2025-06-20T11:07:27+00:00

Some of them were introduced by mass-removal of S = WORKDIR/git assignments; rather than try to fix up (or redo) just these, I've run this sed command over the whole tree: sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc` The rationale is that more than one empty line is wasting vertical screen space, and does nothing for readability. (From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: set S to be in UNPACKDIR in recipes that explicitly set S

2025-06-20T11:07:26+00:00

(From OE-Core rev: 7321cc17ae5483f17fe9cdffea7b62acd9d9c3a2) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove S in recipes that fetch from git via setting BB_GIT_DEFAULT_DESTSUFFIX

2025-06-20T11:07:26+00:00

Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX is set to match S from bitbake.conf (which itself is set to match typical tarball releases). A few recipes are setting S to a sub-directory of the git tree and need to be adjusted accordingly. bzip2 recipe is fetching a tarball and separately cloning tests; adjust the recipe to put the latter into 'bzip2-tests', instead of 'git'. devupstream.bbclass no longer needs to rewrite S, and is adjusted accordingly. Adjust scripts/lib/recipetool/append.py to not hardcode 'git' as unpack destination. Adjust kernel-yocto.bbclass to use the git unpack variable instead of hardcoding 'git' (there's also removal of repetition of string constants and a correction of workdir/unpackdir mismatch in one of the if-else branches). Ensure build-appliance-image recipe does not use 'git' as checkout directory for poky repo, but rather explicitly name it 'poky'. Ensure reproducible.py code that looks for git repositories does not hardcode 'git' but uses the destination set by BB_GIT_DEFAULT_DESTSUFFIX. Ensure recipetool does not write out unneeded S settings into newly created recipes that fetch from git. Adjust selftest to not hardcode 'git' as unpack directory. (From OE-Core rev: f80c07019ddadaf9c5fb890faabfda7920ecd15e) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

boost: add process library

2025-05-27T08:01:16+00:00

This fixes an error seen with current wesnoth: | ../build/tmp/work/corei7-64-poky-linux/wesnoth/1.19.12/recipe-sysroot-native/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/15.1.0/ld: src/libwesnoth-common.a(filesystem.cpp.o): in function `boost::process::v2::environment::detail::is_executable(boost::filesystem::path const&, boost::system::error_code&)': | /usr/include/boost/process/v2/detail/environment_posix.hpp:81:(.text._ZN5boost7process2v211environment15find_executableINS2_12current_viewEEENS_10filesystem4pathES6_OT_[_ZN5boost7process2v211environment15find_executableINS2_12current_viewEEENS_10filesystem4pathES6_OT_]+0x24c): undefined reference to `boost::process::v2::environment::detail::has_x_access(char const*)' | collect2: error: ld returned 1 exit status | ninja: build stopped: subcommand failed. (From OE-Core rev: 6530896d40c403039e5ab8f2e09c2cba908c26e4) Signed-off-by: Markus Volk Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

boost: upgrade 1.87.0 -> 1.88.0

2025-05-13T09:29:20+00:00

(From OE-Core rev: 2aaa023d0a55cce49b4d6bad53137c97386d31bf) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie

boost: Use PN/BPN for naming of packages

2025-03-03T18:01:30+00:00

Rework the anon Python so that it doesn't expect to find non-MLPREFIXed FILES overrides which are then mapped into MLPREFIXed versions, this allows the apparent hardcoding of boost-{test,serialization} to be written more naturally (and is significantly less surprising). With this, and a change to lookup ${BPN} when generating split package names, generating an explicitly versioned boost package (e.g. "boost-1.82") alongside the main boost package ("boost") can be done by copying/renaming the older recipe. This is useful when upstream code hasn't yet been ported to newer boost and an older version is required. (From OE-Core rev: b0770990a8b332dd2de802091164c9506882a465) Signed-off-by: Alex Kiernan Signed-off-by: Richard Purdie

boost: add charconv lib

2025-03-03T18:01:29+00:00

In boost 1.85 a charconv implementation in c++11 was added [https://www.boost.org/doc/libs/master/libs/charconv/doc/html/charconv.html] This is already used in real life and e.g. building the current wesnoth release fails with: | /usr/src/debug/wesnoth/1.19.9/src/utils/charconv.hpp:57:(.text+0x238b): undefined reference to `boost::charconv::to_chars(char*, char*, double, boost::charconv::chars_format)' Add charconv to BOOST_LIBS to provide the library (From OE-Core rev: 42d14c130f2159c1d9ea314acc93142e6ccb2761) Signed-off-by: Markus Volk Signed-off-by: Richard Purdie

boost: update 1.86.0 -> 1.87.0

2025-01-10T11:10:00+00:00

Backport a kea patch to address 1.87.0 compatibility. (From OE-Core rev: ac328183d4592ad146c41e48c2c92d1dbb53a894) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie