[yocto] Is the build system SCM sensitive?
Gary Thomas
gary at mlbassoc.com
Mon Oct 27 15:26:22 PDT 2014
On 2014-10-27 14:07, Burton, Ross wrote:
>
> On 27 October 2014 19:40, Gary Thomas <gary at mlbassoc.com <mailto:gary at mlbassoc.com>> wrote:
>
> I think I know what triggered this - a recent change in bitbake.conf
> redefined BUILD_CPP (and others). I had merged this change some six
> hours before my strange build and had been building many other recipes
> (also python with a similar set of dependencies) a number of times
> before I touched the python-pygtk recipe. Some dependency in that
> recipe set off the rebuild storm that my other recipes had not.
>
>
> Ah yes, welcome back to master. There's been stuff building up for a while. :)
>
> This is where I point out that master between a release and M1 is known to be "volatile". Whilst we obviously endeavour for it to be always buildable, deep and fundamental changes
> will be going in sooner rather than later.
This doesn't bother me - I expect it. What took me by surprise
was when the behaviour radically changed from what I had seen
all day. Totally explainable, but unexpected nonetheless.
>
> (ie this might be time to dust of my libexecdir-changing series)
Go for it :-)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
More information about the yocto
mailing list