I think before those fixes, target rust would not even build. Now it
builds, but is not verified to work :) One step at a time I suppose,
no need to be perfect upfront, as long as the overall direction is
right.

The correct place for the runtime test would probably be
meta/lib/oeqa/runtime/cases/rust.py and it should do something similar
to meta/lib/oeqa/runtime/cases/gcc.py.

Alex

On Fri, 16 Dec 2022 at 11:42, Alex Kiernan <[email protected]> wrote:
>
> Does anyone actually use target rust? I thought we had some test
> coverage, but I'm failing to find it.
>
> After the thread on stable/beta/nightly, I started playing with it on
> target and so far have:
>
> * we're missing the rustlib/<target>/target.json
> * we don't have gcc/binutils in RDEPENDS so there's no linker
> * no libc-dev/libgcc-dev
>
> I'm not sure how target dev tools ever get used/installed as it's not
> something I've ever touched, so maybe the last one/two are expected?
> But the missing target.json just makes rustc bail on startup - looks
> like 16b4ac3f558f ("rust: Enable nativesdk and target builds + replace
> rust-tools-cross-canadian") might be where it got dropped, just
> checking.
>
> --
> Alex Kiernan
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174736): 
https://lists.openembedded.org/g/openembedded-core/message/174736
Mute This Topic: https://lists.openembedded.org/mt/95707414/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to