Julius,
Julius Werner wrote:
Whenever I want a build without vboot I get really annoyed about this hardcoded dependency, even when vboot is disabled in Kconfig.
Would a patch to make the dependency conditional on Kconfig get accepted?
I should hope so, though I recommend starting a new thread to see if experts on vboot can chime in and explain why this is or isn't a good idea.
vboot is used for more than just boot verification these days, we use it as a sort of generic crypto toolbox for all of coreboot's crypto needs (because it wouldn't make sense to implement, say, SHA-256 algorithms twice). For host utilities in particular, some of these are needed in cbfstool (e.g. for the --hash-algorithm parameter to add a hash attribute to a file), and there is no Kconfig cbfstool so you can't just configure it out if you don't need it.
It is clear that I don't need that functionality when I build a coreboot version without any vboot code, right?
Note that I'm not talking about anything gcc, my question can indeed be considered a tangent of the original thread.
Thanks
//Peter