All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Geuder <jrswdnan22@snkmail.com>
To: yocto@yoctoproject.org
Subject: Re: Moving to Yocto 2.3 - recipe-specific sysroots - improving the documentation
Date: Tue, 30 Oct 2018 15:14:36 +0200	[thread overview]
Message-ID: <87bm7bfuf7.fsf@snkmail.com> (raw)
In-Reply-To: <AM5PR0602MB2802B8C31D3325291398D156B1F00@AM5PR0602MB2802.eurprd06.prod.outlook.com>

On Tue, Oct 30, 2018 at 9:05 AM CHMIELARZ Radoslaw radoslaw.chmielarz-at-leica-geosystems.com wrote:
>
> Hi all,
>
>  
>
> I think the documentation on migrating between Yocto 2.2 and 2.3 needs
> more clarification as to how did the sysroots have changed.
>
[...]
>  
>
> Now when trying to migrate I have noticed that STAGING_DIR is not
> populated any more and this is clearly explained by the
> documentation. What is not explained however is how to get the files
> from other recipes. The documentation simply states that each recipe
> has its own staging directory.
[...]

Have you seen this chapter?

https://www.yoctoproject.org/docs/2.5.1/mega-manual/mega-manual.html#new-sharing-files-between-recipes

(well, that's not 2.3 but the newest one, but I am not aware that
anything significant has changed once more)

The headline promises to answer the question, but at least I don't fully
follow the explanations. They are talking about *the* sysroot. As we
know sysroots are recipe-specifc now. So if we are talking about sharing
files between recipes, we have an "exporting" recipe and an "importing"
recipe, so at least in theory 2 sysroots could be involved. From the
text in the manual I do not understand which one they mean and what they
try to explain.

So yes, I agree that the documentation should be clarified. Unfortunatly
I am not in the situation to suggest the solution.

Regards,

Uwe Geuder
Neuro Event Labs Oy
Tampere, Finland
uwe.gexder at neuroeventlabs.com (Bot check: fix one obvious typo)


  reply	other threads:[~2018-10-30 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 12:38 Moving to Yocto 2.3 - recipe-specific sysroots - improving the documentation CHMIELARZ Radoslaw
2018-10-30 13:14 ` Uwe Geuder [this message]
2018-10-30 21:12 ` Khem Raj
2018-11-05 11:14 ` Burton, Ross

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=87bm7bfuf7.fsf@snkmail.com \
    --to=jrswdnan22@snkmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.