Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <bluelightning@bluelightning.org>
To: Alexander Kanavin <alex@linutronix.de>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build
Date: Mon, 10 Oct 2022 21:22:52 +1300	[thread overview]
Message-ID: <45013311.fMDQidcC6G@linc> (raw)
In-Reply-To: <20220622103312.1098389-1-alex@linutronix.de>

Hi Alex

On Wednesday, 22 June 2022 22:33:06 NZDT Alexander Kanavin wrote:
> There's been a recent discussion about how we can make the Yocto SDK
> experience better [1]. One of the ideas was to eliminate the SDK
> as a separate artefact altogether and simply provide everything
> that the SDK and eSDKs do directly in a yocto build. This does not
> mean that people have to 'learn Yocto', but rather that the integrators
> should provide a well-functioning sstate cache infrastructure (same as
> with minimal eSDK, really), and a few wrapper scripts for setting up the
> build and the SDK environment that run layer setup and bitbake behind the
> scenes.

FWIW I think this is quite clever - well done :)

One question though:

> 2. Run:
> $ bitbake meta-ide-support
> $ bitbake -c populate_sysroot gtk+3
> (or any other target or native item that the application developer would
> need) 
> $ bitbake populate-sysroots

Should this have been "build-sysroots"? "populate-sysroots" doesn't seem to be 
a valid target. It looks like this is in the SDK manual as well.

Cheers
Paul





  parent reply	other threads:[~2022-10-10  8:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 10:33 [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 1/6] toolchain-scripts.bbclass: adjust toolchain_create_tree_env_script to better replicate (e)SDK Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 2/6] meta-ide-support: adjust to provide (e)SDK experience directly in a yocto build Alexander Kanavin
2022-06-23 10:03   ` [OE-core] " Luca Ceresoli
2022-06-23 14:52     ` Alexander Kanavin
2022-06-23 16:41       ` Luca Ceresoli
2022-06-22 10:33 ` [RFC PATCH 3/6] oeqa/sdk: add a test class for running SDK tests directly in a Yocto build Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 4/6] selftest/meta_ide: add a test for running SDK tests Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 5/6] oeqa/sdk: allow epoxy/galculator tests to run in esdk and direct yocto builds Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 6/6] oeqa/sdk: drop the nativesdk-python 2.x test Alexander Kanavin
2022-10-10  8:22 ` Paul Eggleton [this message]
2022-10-10  9:20   ` [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build Alexander Kanavin
2022-10-13  8:43 ` Leon Woestenberg
2022-10-13  8:52   ` 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=45013311.fMDQidcC6G@linc \
    --to=bluelightning@bluelightning.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --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