From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Michael Opdenacker <michael.opdenacker@bootlin.com>,
docs <docs@lists.yoctoproject.org>
Subject: Re: [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation
Date: Wed, 22 Nov 2023 10:30:49 +0100 [thread overview]
Message-ID: <CANNYZj_XcosMZQHswireb1JHJahUvSy1NuHy_3-f3Km8aWwgbg@mail.gmail.com> (raw)
In-Reply-To: <CAH=B7vfs74f-vyx8JGJyfAu3NPa5xwgumsW+_ahMBXnfUmJw2Q@mail.gmail.com>
On Wed, 22 Nov 2023 at 10:18, Alberto Merciai <alb3rt0.m3rciai@gmail.com> wrote:
> Of course
> I'm following the guide
> https://docs.yoctoproject.org/4.0.14/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
>
> create environment file for cross compilation
>
> $ bitbake meta-ide-support
> $ bitbake -c populate_sysroot gtk+3
> # or any other target or native item that the application developer would need
> $ bitbake build-sysroots
>
> then you can open a new terminal and sourcing the file generated by the above steps using
> source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux
>
> go inside the project you would like cross-compile and you get errors
Thanks, now I understand what happened. This feature was actually
never backported to kirkstone (and won't be because of LTS policy - no
new features), but documentation was (mistakenly) updated to state
that it was:
https://git.yoctoproject.org/yocto-docs/commit/?h=kirkstone&id=5e2ec35e3d63f9c73726122fe2b3dd6d6f85a77e
Michael, the bits about meta-ide-suppport/build-sysroots need to be
reverted, before more people get misled.
Alberto, can you check that this works as expected on master or any
more recent release where my commit is present, and the file is set
correctly?
Alex
next parent reply other threads:[~2023-11-22 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231122085438.7328-1-alb3rt0.m3rciai@gmail.com>
[not found] ` <CANNYZj87+-6jte1KYUNg2ueWvsYzxiOQvbTzrCZ_ooo9N7uutw@mail.gmail.com>
[not found] ` <CAH=B7vfs74f-vyx8JGJyfAu3NPa5xwgumsW+_ahMBXnfUmJw2Q@mail.gmail.com>
2023-11-22 9:30 ` Alexander Kanavin [this message]
[not found] ` <CAH=B7vdEtF7f51uRsN9qMcL_80M3zsPfFUsD4v_HCgJdxXLdsQ@mail.gmail.com>
2023-11-22 12:12 ` [PATCH] poky: kirkstone: eSDK: fix build-in eSDK environment file generation Alexander Kanavin
2023-11-22 12:45 ` Alexander Kanavin
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=CANNYZj_XcosMZQHswireb1JHJahUvSy1NuHy_3-f3Km8aWwgbg@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alb3rt0.m3rciai@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).