Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Yeoh, Ee Peng" <ee.peng.yeoh@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Openembedded-core Digest, Vol 86, Issue 203
Date: Wed, 21 Mar 2018 13:42:09 +0200	[thread overview]
Message-ID: <d2cea527-fe44-733b-0d30-c3bde705f31a@linux.intel.com> (raw)
In-Reply-To: <9DDD2658D1FE414E99172D2DB1E4D04335DF9D30@PGSMSX109.gar.corp.intel.com>

On 03/21/2018 10:02 AM, Yeoh, Ee Peng wrote:
> In order to convert this to runtime/testimage, we will need to perform below
> 1) Modify existing crosstap script to inverse the dependency on bitbake -e, provide environment variables required as argument
> 2)  Add additional step outside of testimage to bitbake the systemtap-native
> 
> I would like to propose that we keep this crosstap testcase as oe-selftest instead of runtime/testimage as the extra efforts required and the additional step required to build systemtap-native on the host machine.
> 
> Please let me know your input and suggestion.

Right, there are pros and cons to both options. I think 
testimage.bbclass has a mechanism for adding dependencies inside the 
class, so you don't need an additional step. You can add there something 
like:

TESTIMAGEDEPENDS += "${@bb.utils.contains('TEST_SUITES', 'crosstap', 
'systemtap-native:do_populate_sysroot', '', d)}"

On the other hand, providing right bitbake variables to crosstap script 
may not be possible from command line in the context of testimage.bbclass.

Let me comment on the original patch again.


By the way, it's probably better for you to subscribe to this list as 
individual mails. Digests make it very hard for you to participate in 
discussions, and break the mail threads (e.g. I could have missed this 
email, and no one else can easily see what is it about from the subject).


Alex


      reply	other threads:[~2018-03-21 11:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.18076.1521543183.1653.openembedded-core@lists.openembedded.org>
2018-03-21  0:57 ` Openembedded-core Digest, Vol 86, Issue 203 Yeoh, Ee Peng
     [not found] ` <E0805CCB83E6104E80E61FD34E5788AE5305AF4A@PGSMSX102.gar.corp.intel.com>
2018-03-21  8:02   ` Yeoh, Ee Peng
2018-03-21 11:42     ` Alexander Kanavin [this message]

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=d2cea527-fe44-733b-0d30-c3bde705f31a@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=ee.peng.yeoh@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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