From: "Gao, Liming" <liming.gao@intel.com>
To: "Foster, Matthew I" <matthew.i.foster@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: FDF dependency?
Date: Thu, 16 Mar 2017 01:46:07 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6F09E7@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <3E72E29DAAE6E94BB0236F004CFB699B78989025@fmsmsx107.amr.corp.intel.com>
Matthew:
One solution is to configure those PCDs as PatchablePcd and generate the binary image. Then, consume the binary image AsBuild INF file in the different FDF file.
AsBuild INF can be found in the source build output directory.
Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Foster, Matthew I
> Sent: Thursday, March 16, 2017 2:14 AM
> To: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> Subject: [edk2] FDF dependency?
>
> Is there a compile time dependency on values provided in the FDF file? I am facing a situation where I am using pre-built binaries for
> some modules when building. We had a need to create another FDF file to create a separate flash image with different values, but
> finding that some of the prebuilt binaries must be dependent on values in the FDF it was originally compiled against? Because the
> image is having issues booting. Does anyone have any ideas on what I am missing? For example, perhaps I need to include 2 copies of
> something one for each FDF flavor? Thanks for any help.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-03-16 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 18:14 FDF dependency? Foster, Matthew I
2017-03-16 1:46 ` Gao, Liming [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A89E2EF3DFEDB4C8BFDE51014F606A14D6F09E7@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox