Bug 9643

Summary:

Add a means of showing which variables triggered confighash change

Product:

[Build System, Metadata & Runtime] BitBake

Reporter:

Paul Eggleton <bluelightning>

Component:

bitbake

Assignee:

Richard Purdie <richard.purdie>

Status:

NEW ---

QA Contact:

Severity:

enhancement

Priority:

Medium

CC:

poky.bs.watcher, poky.watcher, randy.macleod

Version:

2.0

Target Milestone:

Future

Hardware:

All

OS:

Multiple

Whiteboard:

OS type for building Yocto:

---

Type of Regression:

---

Verified:

Documentation change:

No (bug/feature does not impact docs)

Attachments:

Description	Flags
Patch to write out contents of hashed config	none

Description Paul Eggleton 2016-05-17 03:01:59 UTC

A few times I have had to figure out why a full reparse has been triggered when I think it shouldn't have been; the only way I've been able to do that was to hack in code that does that. It would be nice if there was a built-in means of doing this so I could see exactly which variable(s) are the culprit.

Comment 1 Richard Purdie 2016-05-19 14:43:11 UTC

This sound like a great idea but I'm not sure how to do it. Which code changes did you find useful to debug this? We really need a better proposal before we can commit to do something here...

Comment 2 Paul Eggleton 2016-05-23 04:45:10 UTC

Created attachment 3183 [details]
Patch to write out contents of hashed config

Luckily I had stashed the changes last time I needed to do this - I've attached the patch. Obviously with this I had to diff the files externally after having run bitbake in the two configurations.