binman build questions
sjg at chromium.org
Sat Aug 22 17:09:21 CEST 2020
On Mon, 17 Aug 2020 at 03:54, Jan Kiszka <jan.kiszka at siemens.com> wrote:
> Hi Simon,
> studying the binman integration, some questions/issues popped up:
> # Timestamp file to make sure that binman always runs
> .binman_stamp: FORCE
> @touch $@
> A reason is not provided, neither here nor in the commit log. Is it
> because external blobs may have changed? I suppose the binman step is
> always reproducible, right?
Yes we cannot control where everything comes from and there is no
mechanism to check for changes in external blobs at present. So we
need to do this each time.
Yes the step should be reproducible.
> Furthermore, files generated by binman are not properly cleaned. I have now
> fit at 0x280000.fit
> fit at 0x280000.itb
> in my build folder after make clean, also that .binman_stamp. The target
> images are only cleaned when they happen to carry a well-known name -
> that relates to .
> I would suggest to give all intermediate files the same prefix, say
> ".binman_", so that they can be added to the clean rule. Makes sense?
> But  still needs some idea.
I'm not too keen on a prefix as it will make everything look the same.
Perhaps binman could output a list of files that it generated? Then
the Makefile could look for that list and remove the files also.
At present binman does not distinguish between files that produce a
final output and those that can be used to debug intermediate outputs.
BTW I do suggest avoiding in-tree builds where possible.
More information about the U-Boot