On Jul 17, 2014, at 10:20 AM, Kinney, Michael D
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
On Jul 17, 2014, at 8:20 AM, [email protected] wrote:
> 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
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 ar
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
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] s
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.
