Age | Commit message (Collapse) | Author |
|
The python3-cryptography recipe has a lot of tests and uses a large
amount of memory. It is slow (> 30 seconds).
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
poetry.core.masonry.api is one of the common PEP-517 build backends.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
A PEP 517 build backend implementation developed for Poetry. This project
is intended to be a light weight, fully compliant, self-contained package
allowing PEP 517 compatible build frontends to build Poetry managed projects.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography ptest.
This recipe needs to be kept in lock-step with the version of
python3-cryptography.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography ptest.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
* inherit new setuptools_rust class (which inherits new pyo3 class, which
inherits cargo and python3-dir).
* RDEPENDS on python3-pytest-subtests for ptest
* Copy pyproject.toml for ptest as it defines the pytest.marker(s) needed
* Use 'cargo bitbake' to generate the crate:// SRC_URIs
- Needed some hacks to the Cargo.toml in src/rust/ to make this work (probably
only package.repository was strictly required):
[package]
description = "cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, message digests, and key derivation functions."
homepage = "https://github.com/pyca/cryptography"
repository = "https://github.com/pyca/cryptography"
* Add patches to src/rust/Cargo.toml to fix cargo errors including pem version
* Add check-memfree.py to ptest to check for sufficient free memory
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
setuptools-rust is a plugin for setuptools to build Rust Python extensions
implemented with PyO3 or rust-cpython.
Compile and distribute Python extensions written in Rust as easily as if
they were written in C.
This class inherits pyo3.bbclass (and therefore cargo.bbclass) and
setuptools3.bbclass to make it easier to build Python modules with Rust
extensions.
Need to call pyo3_do_configure to properly setup the PyO3 environment
for cross-compiling.
Need to call cargo_common_do_configure to setup cargo_home/config so
that the linker properly finds e.g. crti.o and crtbeginS.o
It is strongly recommended to provide crates needed for your recipe
using the crate:// fetcher. This can be helped with the cargo-bitbake
command [1].
If you choose not to use the crate fetcher, bitbake vendoring will not
work with setuptools-rust, as it errors out immediately because it cannot
find pyo3 or some other crate. The (strongly discouraged) workaround for
this is to set:
CARGO_DISABLE_BITBAKE_VENDORING = "1"
[1] https://crates.io/crates/cargo-bitbake
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
PyO3 provides Rust bindings for Python, including tools for creating native
Python extension modules. Running and interacting with Python code from a
Rust binary is also supported.
This class sets up the cross-compilation environment.
Export PYO3_CROSS, PYO3_CROSS_LIB_DIR, PYO3_CROSS_INCLUDE_DIR and CARGO_BUILD_TARGET
to inform tools like setuptools-rust we are cross-compiling.
Export RUSTFLAGS so cargo can find 'std' and 'core' for target
Dynamically generate PyO3 config file and export PYO3_CONFIG_FILE
absolute path. This is the trick that finally made pyo3 work.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Dependency for python3-cryptography 3.4.x+
Only native rustc is supported at this time in oe-core,
therefore it makes no sense to try to build for target.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
|
Add script to safely generate the fixture files from a table
[YOCTO #14759]
(Bitbake rev: ec5e9fff8f71ba81bf5e9207abcd3011d63d86d9)
Signed-off-by: David Reyna <David.Reyna@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
'Dunfell' and 'Gatesgarth'.
[YOCTO #14757]
(Bitbake rev: 49308d1db4f7af81e31db21dc8954947de5976c7)
Signed-off-by: David Reyna <David.Reyna@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
PIP_INSTALL_PACKAGE isn't used anymore, so remove all instances of it
from the recipes.
(From OE-Core rev: 15baf24f750ab2c8b0a46d4a3bf2ae9bfa3d0aff)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Use :append instead of += so that recipes can assign to RDEPENDS:${PN}.
This fixes missing RDEPENDS for sixteen recipes in oe-core alone.
Also instead of using obscure inline Python we can just use the
class-target override.
(From OE-Core rev: c4ecd63593df2ffd5c1b7ae1c50652ca57ebe219)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Include all available modules If 'all' is present in GRUB_BUILDIN variable.
To achieve this we need to search for all .mod files in ${B}/grub-core/ and
pass them to grub-mkimage command.
Also, add the verbose option to grub-mkimage.
(From OE-Core rev: ed1bf9aa0af8c12905cf8332bbbb212ab158fe3c)
Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Brings in these fixes
* 391b270 unistd: add __close
* 8af2ff2 random_r: set `x` before calling savestate_r
* cca99e8 wchar: add __mbrlen
* 59e99e9 random_r: Add reentrant random functions from LSB
* 6461276 gnulib: Add __fdelt_warn alias
(From OE-Core rev: f2bc34d68b29077d548e280a25b19f38da126d00)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
See here:
https://www.isc.org/download/
https://kb.isc.org/docs/aa-00896
(From OE-Core rev: d3756fd781730847f9d9576d70424b0a7b3e1840)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Weston will not configure successfully unless wayland
is a distro feature.
(From OE-Core rev: bc72eb17b74606514694a6655d65dab9b2ee96e8)
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 2bf6a0ca9fdf639418646700b20b65c9960efdbe)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
We need to set nobranch=1 as the 0.6.4 tag isn't on any branches at
present.
(From OE-Core rev: 5637ebe76885c21c2c3f975b4f412b02f9e02456)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Overlayfs-etc is useful if the rootfs is read-only. One reason to have
the rootfs read-only is to allow image based updating.
Image based updating will change the underlying root file system, which
is unsupported by overlayfs when with some mount options [1].
This disables those options.
[1] https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html?highlight=overlayfs#changes-to-underlying-filesystems
(From OE-Core rev: 13a057d6ffc3110f891224d7af9455b53581e8a8)
Signed-off-by: Claudius Heine <ch@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Make it easier to see what is happening by wrapping the overly long
lines in the preinit file for the overlayfs-etc.
(From OE-Core rev: 2e116bbc1afbc571b99f2605839e3c90839471be)
Signed-off-by: Claudius Heine <ch@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Take inspiration from the ebtables recipe in meta-networking and omit
installation of etc/ethertypes, since it is provided by netbase. If we
don't do this, the following error occurs during build:
Error: Transaction test error:
file /etc/ethertypes conflicts between attempted installs of
iptables-1.8.7-r0.core2_64 and netbase-1:6.3-r0.noarch
(From OE-Core rev: 297fde1a6fc9ddf12bb4b0cba1d5b03664a3f378)
Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Several recipes are duplicating the same bootstrap logic for installing
a wheel without using any tools. Add an implementation to
pip_install_wheel to centralise the code, and remove the duplicated code
from the following recipes:
- python3-flit-core
- python3-pip
- python3-setuptools
- python3-wheel
(From OE-Core rev: d5d702a2cd06f863340f8e4cdce0904c9d86384d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This recipe inherits setuptools_build_meta which already depends on
python3-setuptools-native.
(From OE-Core rev: 5d514b5dbd09ce059047d849d5b7cc2b2327564d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
PIP is not needed by this class directly, but is used by
pip_install_wheel which already depends on python3-pip-native.
(From OE-Core rev: 2f18b35b8da5dad471c325138be52191412e4100)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 41ccf5b38506608032754beaff393f74e0403fd1)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Like stdlib, these options are also used to select runtime libraries by
clang driver
(From OE-Core rev: 6d2035b9017552f050e53add0b3ef4090141fc5e)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Ensures the configure time tests are compiled/linked with the Options
that it will be using to build.
(From OE-Core rev: 6d01bb24f198710b7acb49c43a8a813b6e01ed14)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
After the override syntax change, toaster isn't working correctly. This
is because it uses IMAGE_INSTALL_append instead of IMAGE_INSTALL:append.
This tweaks the code accordingly to fix this.
I have a suspicion that exiting toaster databases may struggle with
the change and there are some migration steps missing for the whole
overrides syntax change step.
(Bitbake rev: befc93c3e03a9b1a2b630cd5badcda756fe6cd28)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
bitbake -e is not showing variable history correctly for all variables.
The issue was triggered by the change to knotty to default to enabling
variable tracking in the base datastore but that exposed another issue.
The real problem is that calling reset() inside cooker reverts to the
data tracking enabled by the UI for the base datastore, then turns
off tracking. In the case of the environment printing code, it needs
it to be left on.
Tweak the code to ensure data store tracking really is enabled.
The code here is clearly a bit of a mess but this at least fixes a
clear regression until more invasive improvements can be made.
(Bitbake rev: 9596bffc9903f023d1cc97ce531ddb1cf010c4d7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* Use max() to clamp progress to >= 0.
* Be consistent when evaluating self.quiet (treat it as a boolean).
(Bitbake rev: 160f71372ff93894d9314619e9d3b547c1f3cda3)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In commit 8055ec36 (knotty: Improve setscene task display) the setscene
tasks got their own line in the task output. However, the progress bar
code does not handle newlines in its widgets, so the length of the
setscene line was included when calculating how much space is available
for the progress bar of the running tasks, making it much too short.
Instead of trying to teach the progress bar code to handle newlines,
separate the output of the setscene tasks from the progress bar for the
real tasks.
(Bitbake rev: a41f7792f17acdba8c7ea83b79e413ae6a49da68)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
finish
Use pluralise() to correct the grammar, and drop the colon at the end if
runnning in quiet mode.
(Bitbake rev: 57396289f935892390c11afe95f3eede28fd80e7)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(Bitbake rev: bf1de5988698c797403ecd30edda99a76e9c02dd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The conflict with the `package-managment` only happens if the
`overlayfs-etc` class overwrites `/sbin/init`, which is not the case
when `OVERLAYFS_ETC_USE_ORIG_INIT_NAME` is set to `0`.
(From OE-Core rev: c577382c6d155b3a784d06e4c916783cde7165c8)
Signed-off-by: Claudius Heine <ch@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The 'FILES:${PN}' array is missing the systemd unit dir prefix causing
them to not be packaged and the build fails with the
`installed-vs-shipped` error.
This adds the `systemd_system_unitdir` variable in front of every unit
file added with this class.
(From OE-Core rev: d19166cbc567be0803eaf8d0a2a20f44758aae7b)
Signed-off-by: Claudius Heine <ch@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
ANGLE's copy of khrplatform.h is not uptodate with mesa/khronos khrplatform.h
which uses MESA_EGL_NO_X11_HEADERS which is now renamed in newer headers to
EGL_NO_X11 from mesa/khronos headers, however this define is
relatively new and 3D stacks do not have this adopted but apps
like qemu and bunch of others depend on it, I guess they assume mesa.
One can argue that its better to fix the 3D stacks to behave
like mesa but this means every BSP using these stacks will need to
carry such a fix.
https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/include/EGL/eglplatform.h
This patch helps with that
(From OE-Core rev: 4f6b987705a624da3304cb559b885c4352f9b517)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There is use of MESA_EGL_NO_X11_HEADERS which is now renamed in newer headers to
EGL_NO_X11 from mesa/khronos headers, however this define is
relatively new and 3D stacks do not have this adopted but apps
like qemu and bunch of others depend on it, I guess they assume mesa.
One can argue that its better to fix the 3D stacks to behave
like mesa but this means every BSP using these stacks will need to
carry such a fix.
https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/include/EGL/eglplatform.h
(From OE-Core rev: 8c9d0bc4eb2784a3defa047e509d96e0eb521c03)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|