Re: [Openembedded-architecture] proposal: build pipelines in bitbake-setup

Alexander Kanavin <[email protected]>
Newsgroups org.openembedded.lists.bitbake-devel,org.yoctoproject.lists.yocto
Message-ID <CANNYZj9=Qap1AsWfgFgEforE17Gz8ft8fNz4hJcU4Y=zmTKDZA@mail.gmail.com>
On Wed, 6 May 2026 at 12:23, Daiane Angolini
<[email protected]> wrote:
> > 6. Run a pipeline, stopping after a particular step:
> > $ bitbake-setup build <pipeline-name> --stop-after <step-name>
> >
> > Etc. How's this looking?
> >
>
> I like the term `steps`. I would like to add that this should be
> optional, not required. One can still decide to avoid creating a
> pipeline.

Yes of course.

> Regarding a setup tool for builds, why not use `bitbake
> <pipeline-name>` instead of `bitbake-setup build <pipeline-name>`?

bitbake operates on recipes using a well-known command line interface.
We can't bolt on something entirely different.

That said, pipeline functions don't have to be in bitbake-setup, they
can be in a separate tool (Trevor mentioned that 'bitbake-setup' as a
name doesn't fit that functionality very well). I just don't have any
ideas off the top of my head. 'bitbake-pipeline' ?

Alex
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.