public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: adrian.freihofer@gmail.com
To: alex.kanavin@gmail.com, adrian.freihofer@siemens.com
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH v2 1/2] bitbake: add --skip-deps option to re-run tasks directly
Date: Wed, 31 Dec 2025 12:00:33 +0100	[thread overview]
Message-ID: <55d314c3c6bd3e72c3ff972927dac0169d431982.camel@gmail.com> (raw)
In-Reply-To: <CANNYZj_RiybYM31_uwwYZx+kNz_QLs8Ud4yZ1DXfL9RGU1gP-g@mail.gmail.com>

Hi Alex

On Wed, 2025-12-31 at 10:11 +0100, Alexander Kanavin via
lists.openembedded.org wrote:
> On Tue, 30 Dec 2025 at 16:36, Adrian Freihofer via
> lists.openembedded.org
> <adrian.freihofer=siemens.com@lists.openembedded.org> wrote:
> > This is aimed at development workflows (for example devtool ide-
> > sdk)
> > where an IDE or developer wants to re-run a single task (such as
> > do_install) and then deploy or debug it on a target without
> > rebuilding
> > or executing unrelated dependent tasks.
> 
> The patch is horribly invasive, and I'm afraid the premise for it is
> shaky, and should've been discussed here first.

We are discussing this since a very long time. My previous attempt is
here:
https://lists.openembedded.org/g/openembedded-core/message/223669.

With the new attempt I'm trying to follow the advice from Richard to
add a feature to bitbake which allows to address this use case in a
generic way.

> 
> Can you formulate the problem more specifically? What are those
> unrelated dependent tasks? Why do we want to skip them? They are in
> the dependency tree for a reason: so that configure/compile/install
> can run without error. Even if compile is replaced with some kind of
> IDE-specific re-implementation, it still needs those pieces.

If compile is done by the IDE, there is no need for doing it again.
Resolving the full dependency chain is not what an SDK should do.
That's very important.

Reagrds,
Adrian

> 
> Alex
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#18665):
> https://lists.openembedded.org/g/bitbake-devel/message/18665
> Mute This Topic: https://lists.openembedded.org/mt/116998957/4454582
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/bitbake-devel/unsub [adrian.freihofer@gmail.com
> ]
> -=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2025-12-31 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 15:32 [PATCH v2 0/2] bitbake --skip-deps feature AdrianF
2025-12-30 15:32 ` [PATCH v2 1/2] bitbake: add --skip-deps option to re-run tasks directly AdrianF
2025-12-31  9:11   ` [bitbake-devel] " Alexander Kanavin
2025-12-31 11:00     ` adrian.freihofer [this message]
2025-12-30 15:32 ` [PATCH v2 2/2] tests/runqueue: cover --skip-deps AdrianF

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=55d314c3c6bd3e72c3ff972927dac0169d431982.camel@gmail.com \
    --to=adrian.freihofer@gmail.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=alex.kanavin@gmail.com \
    --cc=bitbake-devel@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