Ross, Oh. I did not realize bitbake.conf was parsed multiple times. I thought it was parsed once, which is why I was confused.
Thanks for clarifying. Lewis -----Original Message----- From: Burton, Ross <[email protected]> Sent: Thursday, January 24, 2019 4:22 AM To: Muhlenkamp, Lewis <[email protected]> Cc: openembedded-devel <[email protected]> Subject: Re: [oe] DATETIME seems to be getting updated On Thu, 24 Jan 2019 at 04:32, Muhlenkamp, Lewis <[email protected]> wrote: > It appears that the DATETIME variable is being updated. From what I read > this should not be happening, correct? DATETIME is defined as follows: DATE := "${@time.strftime('%Y%m%d',time.gmtime())}" TIME := "${@time.strftime('%H%M%S',time.gmtime())}" DATETIME = "${DATE}${TIME}" So every time bitbake.conf is parsed, the datetime is updated. This happens once for the main process, and then again for every worker that bitbake spawns. You can silence the 'metadata changed' errors by using vardepsexclude to mark it as a variable that can change (grep oe-core for examples of using DATETIME and vardepsexclude). Ross -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
