On Thu, 2 Nov 2023 at 10:02, Alexander Kanavin via
lists.yoctoproject.org
wrote:
> So here's what I'd like to try:
>
> - write a new populate_build_replica task that writes a few things
> under ${WORKDIR}/replica
> -- setup-layers json and script
> (another option is to copy the layer trees
On Thu, 2 Nov 2023 at 09:32, wrote:
> Sorry for repeating some parts which we already had in other emails.
> But I tried to summarize the lengthy discussion a bit in one place.
So here's what I'd like to try:
- write a new populate_build_replica task that writes a few things
under
On Wed, 2023-11-01 at 18:28 +0100, Alexander Kanavin wrote:
> On Wed, 1 Nov 2023 at 16:45, wrote:
> > I think these differences between SDK and bitbake environment are
> > no
> > longer required and they have been problematic. I would try to make
> > the
> > bitbake environment usable like the
On Wed, 1 Nov 2023 at 16:45, wrote:
> I think these differences between SDK and bitbake environment are no
> longer required and they have been problematic. I would try to make the
> bitbake environment usable like the eSDK environment was without trying
> to replicate all the details of the eSDK
Hi Richard, hi Alex
On Mon, 2023-10-30 at 14:07 +, Richard Purdie wrote:
> On Mon, 2023-10-30 at 14:50 +0100, Alexander Kanavin wrote:
> > On Thu, 14 Sept 2023 at 14:56, Richard Purdie
> > wrote:
> > > There are design elements to this work. We need to work out how
> > > we can
> > > make
On Mon, 30 Oct 2023 at 15:07, Richard Purdie
wrote:
> > a) esdk sets a number of variables from its initialization script that
> > aid with cross-compiling components directly (e.g. the core use case
> > of SDKs). Normal mode doesn't do that, but recently added
> > meta-ide-support will generate
On Mon, 2023-10-30 at 14:50 +0100, Alexander Kanavin wrote:
> On Thu, 14 Sept 2023 at 14:56, Richard Purdie
> wrote:
> > There are design elements to this work. We need to work out how we can
> > make eSDK and "normal" builds more similar and less of an overhead to
> > switch between one and the
On Thu, 14 Sept 2023 at 14:56, Richard Purdie
wrote:
> There are design elements to this work. We need to work out how we can
> make eSDK and "normal" builds more similar and less of an overhead to
> switch between one and the other. A "bblock all" command does partly
> get you to an eSDK
On Thu, 14 Sept 2023 at 21:54, Richard Purdie
wrote:
> The tools are already supposed to support doing this with local file
> sstate sources, they just do a bad job at getting the diffs right. One
> intent of this work item was to try and understand why they don't work
> and address that so at
Unless I missed something, I think I fixed all comments from RP on the
branch I force pushed :)
Cheers
Julien
Le mer. 20 sept. 2023 à 16:31, Alexander Kanavin
a écrit :
>
> That’s great to hear! When you have a new patch set please post it here. I
> think there’s also a new reply from RP that
That’s great to hear! When you have a new patch set please post it here. I
think there’s also a new reply from RP that you need to consider.
Alex
On Wed 20. Sep 2023 at 16.25, Julien Stephan wrote:
> Hi Alexander,
> About bblock tool: I just force pushed my branch on poky-contrib
>
Hi Alexander,
About bblock tool: I just force pushed my branch on poky-contrib
(https://git.yoctoproject.org/poky-contrib/log/?h=jstephan/bblock),
trying to fix an autobuilder issue reported by Alexandre Belloni.
I am still working on this, and I would be very happy to get this merged :)
Cheers
On Thu, 14 Sept 2023 at 21:54, Richard Purdie
wrote:
> Effectively those "configs" are what the eSDK is, you're just proposing
> a server side set of them rather than a built copy. In many ways that
> could be useful way of possibly rethinking the way the eSDK works.
>
> So in that sense I like
On Thu, 2023-09-14 at 20:51 +0200, Alexander Kanavin wrote:
> On Thu, 14 Sept 2023 at 14:56, Richard Purdie
> wrote:
> > For the task signatures, we need to think about some questions. If I
> > make a change locally, can I query how much will rebuild and how much
> > will be reused? There is
On Thu, 14 Sept 2023 at 14:56, Richard Purdie
wrote:
> For the task signatures, we need to think about some questions. If I
> make a change locally, can I query how much will rebuild and how much
> will be reused? There is bitbake --dry-run but perhaps it is time for a
> an option (or dedicated
On Thu, 2023-09-14 at 13:52 +0200, Alexander Kanavin wrote:
> On Tue, 12 Sept 2023 at 16:44, Stephen Jolley wrote:
> > Alexander Kanavin will be working on the core workflow topic
>
> I am now ready to start doing this, but before I do, I'd like to
> decompose the subject into manageable tasks
16 matches
Mail list logo