Hi Brian, Thanks for the recommendation and will include the ability to compare DSC & FDF files as well. I think adding some verification tools is definitely a great idea and will put this down on my to-do list.
Everyone else, are their tools that you would like to see - it may take some time to get to them, but we can always start a discussion. Cheers, Larry -----Original Message----- From: Brian J. Johnson [mailto:[email protected]] Sent: Friday, September 19, 2014 10:59 AM To: [email protected] Subject: Re: [edk2] [RFC] Update INF specification On 09/19/2014 12:10 PM, Hauch, Larry wrote: > > In order to facilitate validation of INF files, we will also like to > create a new tool that can be used for content (not format) validation > of INF and DEC files. This tool would take two files as arguments, > either DEC or INF files, and do an object level comparison. > > I would also like to know if we should also provide the ability > (option > flag) to process two different directory trees as part of this tool? > > Please let me know if there are other features that should be included > here, such as what you would like to see from adding a -v, --verbose flag. > It would be handy to have something which could compare DSC files as well. Often an OEM's platform is based on a reference design from a silicon vendor. It would be handy to be able to see what had changed between the shipping platform and the reference design: modules added and removed, library instances changed, etc. It would be even more handy to have a tool to sanity check DSC vs FDF files, to find INF files listed in one but not the other. (I know, not everything that gets built necessarily needs to go in the firmware image, and not everything in the image is built from a DSC. But in most cases, a mismatch is an error.) As it is, if I add an INF to the FDF but not the DSC, I get a cryptic error message. And if I add it to the DSC but not the FDF, there's no build-time error at all: the module is just mysteriously missing from the firmware, and I need to determine this the hard way by examining the boot output. Sorry, that's not quite what you were asking about. But as long as you're writing tools.... Thanks, -- Brian Johnson -------------------------------------------------------------------- Q. How many software engineers does it take to change a light bulb? A. That's a hardware problem. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
