Re: overriding variables from cmdline used in fdf broken?

[Michael Zimmermann <sigmaepsilon92@gmail.com>]

I just tested it again and apparently everything is working just fine now.
So either, I've done something wrong in past or you guys have already fixed it.

Sorry for not testing before bumping this old thread.

Thanks
Michael

On Mon, Mar 13, 2017 at 3:13 AM, Gao, Liming <liming.gao@intel.com> wrote:
> 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