On Thu, 2018-07-26 at 09:22 -0500, Matt Hoosier wrote:
> On Wed, Jul 25, 2018 at 4:58 PM Richard Purdie
> wrote:
> Your advice about BB_DONT_CACHE does cause reparsing to get
> triggered. I can see that in logs.
>
> > and that the
> > task dependency exists. You have the dependency above and
On Wed, 2018-07-25 at 08:47 -0500, Matt Hoosier wrote:
> Quite a while ago I wrote the following message:
> On Tue, Jan 24, 2017 at 11:55 AM Matt Hoosier > wrote:
> > In order to support a use-case that embeds information about the
> > Git revision of Yocto itself that was used to make a build, I
(Cross-posting to bitbake-devel.)
Quite a while ago I wrote the following message:
On Tue, Jan 24, 2017 at 11:55 AM Matt Hoosier
wrote:
> In order to support a use-case that embeds information about the Git
> revision of Yocto itself that was used to make a build, I would like to run
> some
On Wed, Jan 25, 2017 at 3:03 AM, André Draszik wrote:
> On Tue, 2017-01-24 at 11:55 -0600, Matt Hoosier wrote:
> > In order to support a use-case that embeds information about the Git
> > revision of Yocto itself that was used to make a build, I would like to
> > run
> > some
On Tue, 2017-01-24 at 11:55 -0600, Matt Hoosier wrote:
> In order to support a use-case that embeds information about the Git
> revision of Yocto itself that was used to make a build, I would like to
> run
> some arbitrary Python code and dump the results (Git SHA1's, tag names,
> etc) into a
On Tue, Jan 24, 2017 at 9:55 AM, Matt Hoosier wrote:
> In order to support a use-case that embeds information about the Git
> revision of Yocto itself that was used to make a build, I would like to run
> some arbitrary Python code and dump the results (Git SHA1's, tag
In order to support a use-case that embeds information about the Git
revision of Yocto itself that was used to make a build, I would like to run
some arbitrary Python code and dump the results (Git SHA1's, tag names,
etc) into a Bitbake variable.
The idea is that the variable would get consumed