Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.c.nystrom@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] packagegroup-core-standalone-sdk-target: Add qemuwrapper-cross to target sysroot
Date: Thu, 23 Jan 2014 09:26:29 +0100	[thread overview]
Message-ID: <52E0D235.2060605@gmail.com> (raw)
In-Reply-To: <CAP9ODKqHtSfJi9BpH1D7KKCy=DT4GGywcw7sqA1BcdZr28UgUA@mail.gmail.com>

On ons 22 jan 2014 19:33:22, Otavio Salvador wrote:
> On Wed, Jan 22, 2014 at 4:29 PM, David Nyström
> <david.c.nystrom@gmail.com> wrote:
>> On ons 22 jan 2014 19:24:47, Otavio Salvador wrote:
>>>
>>> On Wed, Jan 22, 2014 at 4:15 PM, David Nyström <david.nystrom@enea.com>
>>> wrote:
>>>>
>>>> On 2014-01-22 19:08, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> On Wed, Jan 22, 2014 at 1:48 PM, David Nyström
>>>>> <david.c.nystrom@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Some postinstall scripts use the qemuwrapper script, so to be able to
>>>>>> offline install these packages outside of the bitbake environment, this
>>>>>> script
>>>>>> needs to be exposed also in the SDK.
>>>>>>
>>>>>> This to enable rootfs generation from a package repository using only a
>>>>>> package repository and the toolchain tarball.
>>>>>>
>>>>>> See https://github.com/nysan/rootfs-sandbox for examples.
>>>>>>
>>>>>> Signed-off-by: David Nyström <david.nystrom@enea.com>
>>>>>
>>>>>
>>>>>
>>>>> Shouldn't this be a RDEPENDS of the postinst package?
>>>>>
>>>>
>>>> Do you mean a RDEPENDS on the run-postinsts package ?
>>>> In that case no.
>>>>
>>>> When $D is set, postinstalls interpret this as a offline install,
>>>> some postinstalls call postinstall-intercepts, which in turn use the
>>>> qemuwrapper script _only_ if $D is set.
>>>>
>>>> run-postinsts should be installed if there are postinstalls which failed
>>>> to
>>>> run during the offline install.
>>>>
>>>> Just to clarify this, the qemuwrapper-cross will only be installed to the
>>>> target SDK sysroot, never on the target rootfs.
>>>
>>>
>>> No; in postinstall-intercepts RDEPENDS.
>>>
>>
>> Ah, now I get it.
>> If I do that, will it not end up on the target rootfs ?
>
> I don't think so.
>

1. RDEPENDS_${PN} = "qemuwrapper-cross" wont work since TARGET_ARCH 
detected in qemuwrapper-cross recipe will be SDKMACHINE when
compiled as nativesdk-qemuwrapper-cross. (I know, nativesdk-*-cross 
should not be done).
I have not found a way to retrieve the real target architecture during 
a nativesdk build.

Also, we can't add qemuwrapper to the nativesdk sysroot, since we may 
have mutiple target sysroots which have different
qemuwrapper settings.

Br,
David



  reply	other threads:[~2014-01-23  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 15:48 [PATCH] packagegroup-core-standalone-sdk-target: Add qemuwrapper-cross to target sysroot David Nyström
2014-01-22 18:08 ` Otavio Salvador
2014-01-22 18:15   ` David Nyström
2014-01-22 18:24     ` Otavio Salvador
2014-01-22 18:29       ` David Nyström
2014-01-22 18:33         ` Otavio Salvador
2014-01-23  8:26           ` David Nyström [this message]
2014-01-23 10:52             ` Otavio Salvador

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=52E0D235.2060605@gmail.com \
    --to=david.c.nystrom@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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