On Thu, Jan 8, 2026 at 11:55 PM Alistair Francis via lists.openembedded.org <[email protected]> wrote:
> From: Alistair Francis <[email protected]> > > Allow the user to run the rustavailable kernel make command to determine > if Rust is avaliable for kernel builds. > > Signed-off-by: Alistair Francis <[email protected]> > --- > meta/classes-recipe/cml1.bbclass | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/meta/classes-recipe/cml1.bbclass > b/meta/classes-recipe/cml1.bbclass > index 3c2b4da4af..efbdd2a795 100644 > --- a/meta/classes-recipe/cml1.bbclass > +++ b/meta/classes-recipe/cml1.bbclass > @@ -107,6 +107,15 @@ do_diffconfig[nostamp] = "1" > do_diffconfig[dirs] = "${KCONFIG_CONFIG_ROOTDIR}" > addtask diffconfig > > +python do_rustavailable() { > + oe_terminal("sh -c 'make rustavailable; if [ $? -ne 0 ]; then echo > \"Command failed.\"; fi; printf \"Press any key to continue... \"; read > r;'", > + d.getVar('PN') + ' Configuration', d) > +} > This seems a bit heavy to just determine if rust is available. Since the task is already after do_configure .. why not just check the .config ? Bruce > + > +do_rustavailable[nostamp] = "1" > +do_rustavailable[dirs] = "${KCONFIG_CONFIG_ROOTDIR}" > +addtask rustavailable after do_configure > + > do_showconfig() { > bbplain "Config file written to ${KCONFIG_CONFIG_ROOTDIR}/.config" > } > -- > 2.52.0 > > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#229117): https://lists.openembedded.org/g/openembedded-core/message/229117 Mute This Topic: https://lists.openembedded.org/mt/117170673/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
