From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: Daryl McDaniel <edk2-lists@mc2research.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: Possible Bug in build tools?
Date: Thu, 20 Jul 2017 02:42:12 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51EAFCD3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <054601d300de$cd9fad90$68df08b0$@mc2research.org>
Hi Daryl McDaniel,
It is a bug. Could you help to file it in bugzilla system ? https://bugzilla.tianocore.org/
Best Regards,
Zhu Yonghong
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Daryl McDaniel
Sent: Thursday, July 20, 2017 6:32 AM
To: edk2-devel@lists.01.org
Cc: Gao, Liming <liming.gao@intel.com>
Subject: [edk2] Possible Bug in build tools?
Hello,
I've run into a problem with using INF files for specifying binary components.
According to the INF specification, v1.26, a specification such as:
[Binaries.X64]
PE32|DEBUG/X64/MyDbgDriver.efi|DEBUG
PE32|RELEASE/X64/MyDriver.efi|RELEASE
Should cause "MyDbgDriver.efi" to be included for DEBUG builds, and "MyDriver.efi" to be included for RELEASE builds.
What I am seeing is that, given the above specification, "MyDriver" is included for both DEBUG and RELEASE builds.
The last entry specified seems to be the one selected, regardless of the target.
Am I doing something wrong, or is this really a bug?
Daryl McDaniel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-07-20 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 22:31 Possible Bug in build tools? Daryl McDaniel
2017-07-20 2:42 ` Zhu, Yonghong [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=B9726D6DCCFB8B4CA276A9169B02216D51EAFCD3@SHSMSX103.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