Skip to contentSkip to conversation

Add rust runtime tests

PATCH Alex Kiernan 2 participants 3 messages Dec 26, 2022 2 messages not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

There's something odd happened here. Three of the patches in the previous version I posted look to have been merged in poky, but not oe-core? I thought the flow was from oe-core into poky.

Quoted 67 lines · On Sun, 25 Dec 2022, 21:59 Alex Kiernan via lists.openembedded.org…

This series adds runtime tests for rust and cargo, merges (most of) the include files into the base recipes and fixes target cargo builds.

Also add SDK_TOOLCHAIN_LANGS for selection of target toolchains as part of packagegroup-core-sdk.

Changes in v4:
- Fixup __stack_chk_fail_local in musl-x86
- Add crossbeam atomics fixes for ppc/mips

Changes in v3:
- Switch to packagegroup-core-sdk driven from TARGET_TOOLCHAIN_LANGS (which defaults to SDK_TOOLCHAIN_LANGS)

Changes in v2:
- Drop rust.inc/rust.bb merge, not actually made use of in the change set
- Reorder so cargo test goes after build fixes

Alex Kiernan (11):
rust-llvm: Merge .inc into .bb
rust-llvm: Update LLVM_VERSION to match embedded version packagegroup-rust-sdk-target: Add Rust SDK target packagegroup
packagegroup-core-sdk: Add SDK toolchain language selection support
cargo: Merge .inc into .bb
cargo: Extend DEBUG_PREFIX_MAP to cover vendor
rust: Merge .inc into .bb
rust: Move musl-x86 fix for __stack_chk_fail_local to rust-source
cargo: Override crossbeam-utils with 0.8.14 packagegroup-rust-sdk-target: Add cargo oeqa/runtime/rust: Add cargo test

 meta/lib/oeqa/runtime/cases/rust.py           |  17 ++
 .../packagegroups/packagegroup-core-sdk.bb    |  10 +-
 .../packagegroup-rust-sdk-target.bb           |  14 ++
 meta/recipes-devtools/cargo/cargo.inc         |  69 ------
 meta/recipes-devtools/cargo/cargo_1.66.0.bb   |  80 ++++++-
 meta/recipes-devtools/rust/rust-llvm.inc      |  78 ------
 .../recipes-devtools/rust/rust-llvm_1.66.0.bb |  82 ++++++-
 meta/recipes-devtools/rust/rust-source.inc    |   5 +
 meta/recipes-devtools/rust/rust-target.inc    |  10 -
 meta/recipes-devtools/rust/rust.inc           | 223 ------------------
 meta/recipes-devtools/rust/rust_1.66.0.bb     | 223 +++++++++++++++++-
 11 files changed, 420 insertions(+), 391 deletions(-)
 create mode 100644 meta/recipes-core/packagegroups/
packagegroup-rust-sdk-target.bb
 delete mode 100644 meta/recipes-devtools/cargo/cargo.inc
 delete mode 100644 meta/recipes-devtools/rust/rust-llvm.inc
 delete mode 100644 meta/recipes-devtools/rust/rust-target.inc
 delete mode 100644 meta/recipes-devtools/rust/rust.inc

--
2.39.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#174995):
https://lists.openembedded.org/g/openembedded-core/message/174995
Mute This Topic: https://lists.openembedded.org/mt/95880347/3618097
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#2 lore raw
Quoted 3 lines · Alex Kiernan

There's something odd happened here. Three of the patches in the previous version I posted look to have been merged in poky, but not oe-core? I thought the flow was from oe-core into poky.

I'd attempted to take three of them into master-next to try and move things along a little with testing. It looks like I've messed something up. I'll try and reconcile things, thanks for pointing it out. Not sure how I managed this!

Cheers,

Richard

#4 lore raw
In reply to a message not in the archive
Quoted 9 lines · Richard Purdie via lists.openembedded.org
Quoted 3 lines · Alex Kiernan

There's something odd happened here. Three of the patches in the previous version I posted look to have been merged in poky, but not oe-core? I thought the flow was from oe-core into poky.

I'd attempted to take three of them into master-next to try and move things along a little with testing. It looks like I've messed something up. I'll try and reconcile things, thanks for pointing it out. Not sure how I managed this!

I can only think I ran some commands in the wrong terminal window. The simplest thing for me to do was to bring the branches into sync which I've done, which means some of the series did merge. I don't think that should be a problem and we can build incrementally on it.

Cheers,

Richard