From: "Gao, Liming" <liming.gao@intel.com>
To: "j.oetjengerdes@gmail.com" <j.oetjengerdes@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: VFR IMAGE_TOKEN Macro
Date: Tue, 28 Mar 2017 03:28:32 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D70434C@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPVSGsqfzznuFbiZ3Zc5q0mevbUMi7rS-vvQwFn-044Z+Bir9Q@mail.gmail.com>
Thanks for report this issue. VfrCompiler needs to update to support IMAGE_TOKEN.
Could you help submit one bug in Bugzilla? We need to fix it.
Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Jannis ?tjengerdes
> Sent: Tuesday, March 28, 2017 12:55 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] VFR IMAGE_TOKEN Macro
>
> Hello,
>
> I think I found a bug in edk2, in the buildscripts or vfr to be precisely.
>
> As I don't know what is happening exactly in your build scripts, I'll
> describe here what I expect and what's actually happen (or don't happen).
>
> I am using IMAGE_TOKEN which I use similar to STRING_TOKEN
>
> For example:
>
> if I have:
>
> #image IMAGE_TEST_IMAGE image.bmp
>
> the identifier isn't replaced by an id (s.th. like 0x0001) which is by when
> I'm using strings. The result is that I get an error by vfr compile.
>
> The actual failure is in the .vfr file itself (not in the .uni file).
>
>
> Thank you!
>
> Jannis Ötjengerdes
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-03-28 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 16:54 VFR IMAGE_TOKEN Macro Jannis Ötjengerdes
2017-03-28 3:28 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D70434C@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