public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: paul.barker.ct@bp.renesas.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [master/scarthgap PATCH] meta-ide-support: Mark recipe as MACHINE-specific
Date: Fri, 06 Sep 2024 14:48:45 +0100	[thread overview]
Message-ID: <fd756f4b5ce0b3b2dc38813469a0224047f99a09.camel@linuxfoundation.org> (raw)
In-Reply-To: <17F27A4142F288D2.30374@lists.openembedded.org>

On Thu, 2024-09-05 at 23:40 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Thu, 2024-09-05 at 21:21 +0100, Paul Barker via lists.openembedded.org wrote:
> > meta-ide-support:do_write_test_data dumps the bitbake data dictionary to
> > a file using export2json(). As this obviously includes the value of
> > MACHINE, and other MACHINE-specific variables, the recipe needs to be
> > marked as MACHINE-specific.
> > 
> > Signed-off-by: Paul Barker <paul.barker.ct@bp.renesas.com>
> > ---
> >  meta/recipes-core/meta/meta-ide-support.bb | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/meta/recipes-core/meta/meta-ide-support.bb b/meta/recipes-core/meta/meta-ide-support.bb
> > index d85aa120c08b..7ed422ce4ddb 100644
> > --- a/meta/recipes-core/meta/meta-ide-support.bb
> > +++ b/meta/recipes-core/meta/meta-ide-support.bb
> > @@ -1,6 +1,7 @@
> >  SUMMARY = "Integrated Development Environment support"
> >  DESCRIPTION = "Meta package for ensuring the build directory contains all appropriate toolchain packages for using an IDE"
> >  LICENSE = "MIT"
> > +PACKAGE_ARCH = "${MACHINE_ARCH}"
> >  
> >  DEPENDS = "virtual/libc gdb-cross-${TARGET_ARCH} qemu-native qemu-helper-native unfs3-native cmake-native autoconf-native automake-native meson-native intltool-native pkgconfig-native"
> >  RM_WORK_EXCLUDE += "${PN}"
> 
> Something about this is making our toolchain tests unhappy, e.g.:
> 
> https://valkyrie.yoctoproject.org/#/builders/42/builds/86/steps/12/logs/stdio
> 
> I've not looked into it at all, just reporting what we've need to fix
> in order to be able to consider merging this.

It can be fixed with:

diff --git a/meta/lib/oeqa/selftest/cases/meta_ide.py b/meta/lib/oeqa/selftest/cases/meta_ide.py
index ffe0d2604d1..5a17ca52ea1 100644
--- a/meta/lib/oeqa/selftest/cases/meta_ide.py
+++ b/meta/lib/oeqa/selftest/cases/meta_ide.py
@@ -20,8 +20,8 @@ class MetaIDE(OESelftestTestCase):
         bitbake('meta-ide-support')
         bitbake('build-sysroots -c build_native_sysroot')
         bitbake('build-sysroots -c build_target_sysroot')
-        bb_vars = get_bb_vars(['MULTIMACH_TARGET_SYS', 'DEPLOY_DIR_IMAGE', 'COREBASE'])
-        cls.environment_script = 'environment-setup-%s' % bb_vars['MULTIMACH_TARGET_SYS']
+        bb_vars = get_bb_vars(['MACHINE_ARCH', 'TARGET_VENDOR', 'TARGET_OS', 'DEPLOY_DIR_IMAGE', 'COREBASE'])
+        cls.environment_script = 'environment-setup-%s%s-%s' % (bb_vars['MACHINE_ARCH'], bb_vars['TARGET_VENDOR'], bb_vars['TARGET_OS'])
         cls.deploydir = bb_vars['DEPLOY_DIR_IMAGE']
         cls.environment_script_path = '%s/%s' % (cls.deploydir, cls.environment_script)
         cls.corebasedir = bb_vars['COREBASE']

Whether that is a good/right fix, I'm not sure...

Cheers,

Richard


  parent reply	other threads:[~2024-09-06 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 20:21 [master/scarthgap PATCH] meta-ide-support: Mark recipe as MACHINE-specific Paul Barker
2024-09-05 22:40 ` [OE-core] " Richard Purdie
     [not found] ` <17F27A4142F288D2.30374@lists.openembedded.org>
2024-09-06 13:48   ` Richard Purdie [this message]
2024-09-30 10:23     ` Paul Barker
2024-10-15 12:21       ` Paul Barker
2024-10-15 12:44         ` Steve Sakoman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fd756f4b5ce0b3b2dc38813469a0224047f99a09.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.barker.ct@bp.renesas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox