Remove further code duplication by allowing the main function to be
configurable.
(From OE-Core rev: 2d4b35a0db1220e7a7f1b6776223aa4d40a3f246)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently most of the rust recipes use this code but it is all piecemeal.
Turn the code into a class where things can start to be rationalised. Ultimately
some of the data and python code should be moved to a python library but one step
at a time.
No functionality changes.
(From OE-Core rev: 3795285cbf362e13b8151bfdbe1bce999ac28641)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some of the subtleties in the different codepaths for target rust json generation
were not easy to spot. Start to simplfy the code to make this clearer.
This patch should not have any functionality change although ABIEXTENSION
has to be excluded from the function signature, the triplet would normally
cover anything set there.
(From OE-Core rev: 0f83d959465e0d99f98ade6803281585931d1b02)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Match the code in rust-cross-canadian so that further simplifications
can be considered in future.
(From OE-Core rev: 5cb62d0a33777cb9afb1eea5f736a2580ce50dc7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rust-cross had special handling for armv7 targets but we also need this
for cross-canadian. Merge the code into the main function so everything is
consistent.
Also then fix the arm definition to be arm-eabi since ABI is correctly
being looked up.
(From OE-Core rev: ff3c3dbbd2bf1bb7bb70b55cca203e9eedcf14a8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Based upon a patch from Otavio Salvador <otavio@ossystems.com.br>,
ensure the target json files are written in the correct order with
the most specific last incase it overwrites earlier files if the prefixes
match.
(From OE-Core rev: 1912c4e9e0ecf9655f3b3a41588b54d7956f5899)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When a 'BUILD' target is requested we shouldn't be looking at TARGET_SYS but
at BUILD_SYS. Due to the way rust mangles triplets, we need the HOST_SYS triplet
to work with existing code - fixing that issue is a separate patch.
Also drop the arch_abi argument, it doens't make any sense to a getVar() call
and was a copy and paste error.
Based on a patch from Otavio Salvador <otavio@ossystems.com.br> but separated out
and tweaked.
Fixes: bd36593ba3 ("rust-common: Drop LLVM_TARGET and simplify")
(From OE-Core rev: d554161a045d12411f288394e253c54aa4c1257c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
io_uring is enabled or disabled depending on whether liburing is available,
so add a PACKAGECONFIG to make this explicit, disabled by default.
(From OE-Core rev: daee79639c39ac6278855b35e0ddf71e52dd13f8)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* it's not used by any other recipe AFAIK
* meta-python2 has own copy for python-setuptools there in:
meta-python2/recipes-devtools/python/python-setuptools/0001-conditionally-do-not-fetch-code-by-easy_install.patch
(From OE-Core rev: 3a5898861337eb4934360ef6ae448896ec061e26)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ignore the rmdir cmd if using usrmerge distro feature since the
intention is to delete /lib or /lib64 but not libdir under /usr and
base_libdir = libdir when usrmerge is enabled in distro
(From OE-Core rev: 3b7f6b0e0f1f16f89cd924aac001b4f661c145ca)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
some standalone targets e.g. riscv64-elf disable shared linking for
baremetal ELF ABI in ld, therefore lets make it a static library
(From OE-Core rev: 3c6219dfcbcbde314648ba8cc54a90b32ea1c952)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This disables tests for runtime system specific functions like fcntl
there is no other change seen
+configure:77372: checking for fcntl
+configure:77372: result: yes
In libsttdc++ configure log outputs.
[YOCTO #14803]
(From OE-Core rev: 586b6239252ecf2711930b60f7f0f617e38ac737)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a dummy shared object therefore reduce dependencies further by
not requiring the C startup files, we wont use this shared library for
anything useful anyway
(From OE-Core rev: e1c4953f5587621d4911416c2e9350ad0c27b296)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
And spitted the files for the tests into a -test package
buildhistory:
images/raspberrypi4_64/glibc/core-image-base: IMAGESIZE changed from 208024 to 183660 (-12%)
Changes to images/raspberrypi4_64/glibc/core-image-base (installed-package-names.txt):
python3-pyparsing was removed
python3-pip was removed
python3-setuptools-scm was removed
python3-packaging was removed
python3-typing-extensions was removed
python3-pkg-resources was removed
python3-tomli was removed
python3-setuptools was removed
(From OE-Core rev: d744882251236800412870922b30ddbc70d214e5)
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update:
year updated to 2022
URLs of documentation and repositories changed
URLs of license text changed
List of files covered by the BSD 2-Clause License changed
Changelog:
===========
- Drop support for Python 2.7, 3.5, and 3.6.
- Output changes:
HTML5:
Wrap groups of footnotes in an <aside> for easier styling.
The CSS rule .footnote-list { display: contents; } can be used to restore
the behaviour of custom CSS styles.
- After package installation, the CLI commands python -m docutils and docutils
start the generic command line front end tool.
- Support parsing "Markdown" input with 3rd party parsers myst, pycmark, or recommonmark.
- The default values for the "pep-references", "rfc-base-url", and "python-home"
configuration settings now use the "https:" scheme. The PEP-writer template's
header is updated to fix links and resemble the header of official PEPs.
- Various bugfixes and improvements (see HISTORY).
(From OE-Core rev: 91ffa2d80b959018cb8d531a2ec897dda1b2f691)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Major features since 0.1:
- Implement support for legacy source trees
- Add option to loosen dependency checking
(From OE-Core rev: 5260d81dab757120114e103135dfb4c98443afa3)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes reproducibility issues with multilibs were a different recipe
specific sysroot is used which was leaking into debug symbols in libraries.
(From OE-Core rev: f442edf51e256bd315bd8e4ac4d9fa12b8e9e092)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If gold is enabled as the default linker, it errors trying to link
to our dummy library empty file and this turns off things which should
be present in libstdc++.
For example, _GLIBCXX_HAVE_S_ISREG isn't defined and HAVE_S_ISREG in
libstdc++-v3/config.h isn't set properly.
Instead of just creating an empty file, create an empty elf binary
instead which addresses the issue.
(From OE-Core rev: 2070bcd10aa3a05c96c8501c6a8c1e129fb1d440)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that we're using picobuild, hatchling can bootstrap itself.
(From OE-Core rev: 995d65b2f87a3a4dff3771f049d67ac3fa0397cd)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Calling the PEP-517 API directly mostly works, but sometimes doesn't.
For example we don't verify build dependencies, which led to the cbor2
ugprade silently failing to actually package anything.
The standard frontend is pypa/build, but for source-based distributions
that can be annoying to build as it depends on the following packages:
- tomli
- pep517
- packaging
- pyparsing
Manually bootstrapping those recipes is possible, but tedious.
Picobuild is another frontend (written by myself) which is designed
explicitly to be used programatically by source-based distributions: it
doesn't support builds inside virtual environments as we're building
distribution packages, and it vendors the dependencies for bootstrapping
if they're not available.
Over time more packages are expected to move to using Flit to build
which makes the bootstrapping process slightly easier, and tomli will be
integrated into Python 3.11, so it's possible that in the future we
drop picobuild and switch to build.
This change means the PEP517_BUILD_API variable is obsolete, so remove
it.
(From OE-Core rev: 35104958181d18fd67b73943b9310c813d62b14d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Picobuild is a pico-scale Python PEP517 build frontend, designed to have
minimal dependencies (via vendoring) to be well suited for building
source-based distributions, such as OpenEmbedded.
(From OE-Core rev: cf85bddc2d1ce840fc6f4899b6280e1f39e62e7d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The installer can install itself by simply adding src/ to PYTHONPATH.
As this previously used unzip, we need to disable bytecode as otherwise
the newly packaged .pyc files conflict with the any generated .pyc files
in the sysroot.
(From OE-Core rev: 825176ea8130a50cce221678f6fcba25ac956950)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a method to python_flit_core.bbclass that does a manual build with
flit explicitly, and use that to bootstrap python3-flit-core-native which
can build itself.
(From OE-Core rev: e902578c2c9aacdc83dcfa517bc1e57667fcc460)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Autobuilder workers were non-deterministically enabling capstone
depending on whether the worker had libcapstone installed.
Add PACKAGECONFIG for capstone with default off, since ruby does not
require capstone support.
(From OE-Core rev: a43568be9def6de5a0105a822a79c3c07716ec9c)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a PACKAGECONFIG option for slirp, defaulting to internal. This avoids
the presence of libslirp on the host causing qemu to link against that
instead breaking reproducibility and usability of the binary on hosts
where the library isn't present.
We need to add it to PACKAGECONFIG by default since users do expect slirp
to be enabled in the wider community.
(From OE-Core rev: 5a9a64132bf5ecac9d611d29751226a466c4a2c1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Avoid accidentally linking to the vde library from the host by
adding a PACKAGECONFIG for the option.
(From OE-Core rev: 8839e9540528b0b46c4fb4f95e508f038bcef8b9)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add dependence python3-logging.
Changelog:
=========
* Removed support for Python 3.5
* Fixed an issue where a "ProxyError" recommending configuring the proxy as HTTP
instead of HTTPS could appear even when an HTTPS proxy wasn't configured.
(From OE-Core rev: a8a26a92dfe367472daf086a33a1b30ff6d17540)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
=========
- Add typing_extensions.NamedTuple, allowing for generic NamedTuples on Python <3.11
- Adjust typing_extensions.TypedDict to allow for generic TypedDicts on Python <3.11
(From OE-Core rev: 64e3b4b13a9d3d46e0908125560fbb5339022545)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
