We're currently encouraging an "arms race" with the FLAGS variables since
a recipe might want to set a specific flag for all variants but to do so,
+= won't work due to the assignment in the native/nativesdk class files. This
means recipes are using append.
Since the default variables are constructed out of TARGET_XXX variables and
we redefine these, there is no need to re-define the un-prefixed variables. If
we drop that, the += appends and similar work and recipes don't have to resort
to append.
Change the classes and cleanup a number of recipes to adapt to the change. This
change will result in some flags appearing to some native/nativesdk variants
but that is probably what was originally expected anyway.
(From OE-Core rev: a157b2f9d93428ca21265cc860a3b58b3698b3aa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Refresh python3-maturin-crates.inc
1.6.0 - 2024-06-04
* Detect compiling from Linux gnu to Linux musl as cross compiling in #2010
* Add musllinux support to generate-ci in #2011
* Add uv support to develop command in #2015
* Add support for AIX target in #2030
* Remove rust-cpython support in #2044
* Add a global -v option in #2080
* Detect target based on interpreter for pep517 build-wheel in #2088
* Use base executable when possible in PEP 517 build in #2094https://github.com/pyo3/maturin/compare/v1.5.1...v1.6.0
(From OE-Core rev: 6bfea504150466bb04c47eee834bdcc2c622f26e)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
