public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: 'Michael Zimmermann' <sigmaepsilon92@gmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: overriding variables from cmdline used in fdf broken?
Date: Mon, 13 Mar 2017 02:13:38 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6EECA4@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAN9vWDJmsvDjkmEHTU9LXdrC_vT4Yfu6+112-PiT1U+D2KkfSQ@mail.gmail.com>

Michael:
  I agree this is a bug. Could you enter it into bugzillar?

Thanks
Liming
> -----Original Message-----
> From: Michael Zimmermann [mailto:sigmaepsilon92@gmail.com]
> Sent: Sunday, March 12, 2017 12:44 AM
> To: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> Cc: Zhu, Yonghong <yonghong.zhu@intel.com>; Gao, Liming <liming.gao@intel.com>
> Subject: Re: [edk2] overriding variables from cmdline used in fdf broken?
> 
> I forgot to CC the maintainers back then so I'm doing this now.
> 
> Thanks
> Michael
> 
> On Thu, May 12, 2016 at 11:13 AM, Michael Zimmermann
> <sigmaepsilon92@gmail.com> wrote:
> > Hi,
> >
> > when I override or set a variable using -DNAME=VAL from the build cmdline
> > these are visible to the DSC file only, the FDF continues using the
> > old/undefined values - at least if you use them as a value, i.e.:
> > BaseAddress   = $(FD_BASE)|gArmTokenSpaceGuid.PcdFdBaseAddress
> >
> > is this intended behavior or a bug?
> >
> > Michael

  reply	other threads:[~2017-03-13  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN9vWDKz8bESQVWX6_f_i5cutPPFUWqqL=9ncf228Z6RkDTwoQ@mail.gmail.com>
2017-03-11 16:43 ` overriding variables from cmdline used in fdf broken? Michael Zimmermann
2017-03-13  2:13   ` Gao, Liming [this message]
2017-03-13  6:29     ` Michael Zimmermann
2017-03-13  6:42       ` Zhu, Yonghong

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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6EECA4@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