Re: [edk2-buildtools] Building from Binaries

[Andrew F. <af...@ap...>]

On Jul 17, 2014, at 10:20 AM, Kinney, Michael D <mic...@in...> wrote:

> Jim,
>  
> Can you please provide details or an example that fails when using an AsBuilt INF?  I would like to see if there is something that can be done quickly to resolve your specific issues.
>  
> I agree that tools that do not need to use sources should not fail or generate an error if the sources are not present.  We can investigate this.  I do suspect, as you do, that a common parser is involved, and that parse will need adjustments for tools that do not require sources.
>  

I’d like to see more flexibility too, but how do we tell the difference between this caae and a bug where the DSC and FDF are out of sync?

Thanks,

Andrew Fish

> Thanks,
>  
> Mike
>  
> From: Jim...@De... [mailto:Jim...@De...] 
> Sent: Thursday, July 17, 2014 9:02 AM
> To: Kinney, Michael D
> Cc: edk...@li...
> Subject: RE: Building from Binaries
>  
> Thanks, Mike.
>  
> I understand that and have been down that road. Unfortunately, ACPI tables
> and a couple of other "special" things foiled that approach for me.
>  
> In any case, I would still like to know why GenFds is looking for the presence
> of source files, when it is supposed to assemble the binaries that have already
> been built.  This seems totally wrong.
>  
> Regards,
> Jim
>  
>  
> From: Kinney, Michael D [mailto:mic...@in...] 
> Sent: Thursday, July 17, 2014 10:38 AM
> To: Dailey, Jim; edk...@li...
> Subject: RE: Building from Binaries
>  
> Jim,
>  
> When you build from sources in EDK II, the binaries are generated and an AsBuilt INF is also generated in the build output directory.  The AsBuilt INF does not list the sources and only lists the binaries.  If you use the AsBuild INF in your FDF file, then GenFds will not see a [Sources] section.
>  
> Thanks,
>  
> Mike
>  
> From: Jim...@De... [mailto:Jim...@De...] 
> Sent: Thursday, July 17, 2014 8:20 AM
> To: edk...@li...
> Subject: [edk2-buildtools] Building from Binaries
>  
> I want to be able to supply a directory tree having tools and binaries from
> an already built EDK2 BIOS. This would be useful so that, for example, the
> provider of a driver which is included in the BIOS can rebuild the BIOS with
> newer or different versions of the driver for debug and/or development.
>  
> It seems that GenFds quits when it can't find the first source file listed
> in the first INF in the first FV it encounters in the FDF:
>  
>     Generate Region at Offset 0x0
>        Region Size = 0x470000
>        Region Name = FV
>  
>     Generating FVMAIN_COMPACT FV
>  
>     Generating FVMAIN FV
>  
>  
>     GenFds...
>     <drive>:\<path>\<INF file name>.inf(20): error 000E: File/directory not
>     found in workspace
>             <drive>:\<path>\<include file name>.h
>     NMAKE : fatal error U1077: 'GenFds' : return code '0xe'
>     Stop.
>  
> My question is, why does GenFds care about source files at all when its
> "user manual" states:
>  
>     The output of the first phase of an EDK II build (as defined in
>     the EDK II Build Specification) generates valid PE32/PE32+/Coff
>     image files. GenFds performs the second phase of the build process
>     during which consumes the images generated during the first phase,
>     using statements and rules defined in the FDF file to place the
>     PE32/PE32+/Coff images files into one or more EFI sections.
>  
> GenFds requiring the presence of source files seems like a defect in the way
> the tool behaves or is described in the manual.
>  
> My guess is the problem stems from using "generic" code that not only parses
> the FDF, but delves into the files it includes in a way that is not needed by
> (and in this case is detrimental to the operation of) GenFds.
>  
> Can this be corrected?
>  
> Can you recommend a process to accomplish my goal of building strictly from
> existing binary files?
>  
> Regards,
> Jim
>  
>  
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds_______________________________________________
> edk2-buildtools-devel mailing list
> edk...@li...
> https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel