From: Aleksey Ryzhov <a.ryzhov@yadro.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] Some unpredictable behavior while parsing the FDF file.
Date: Tue, 26 Dec 2023 20:10:04 +0000 [thread overview]
Message-ID: <7b4101c435f24cf6aed865b7040bf2f6@yadro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hello! I'm trying to add the following construct to an FDF file:
DEFINE MY_VAR = FALSE
!if $(MY_VAR)
!include Path/To/Non/Existing/File.inc
!endif
And I get the following error:
GenFds.FdfParser.Warning: The include file does not exist under below directories:
Is this correct FDF parser behavior?
Thanks.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112936): https://edk2.groups.io/g/devel/message/112936
Mute This Topic: https://groups.io/mt/103394871/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 2479 bytes --]
next reply other threads:[~2023-12-28 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 20:10 Aleksey Ryzhov [this message]
2023-12-28 16:09 ` [edk2-devel] Some unpredictable behavior while parsing the FDF file Joey Vagedes via groups.io
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=7b4101c435f24cf6aed865b7040bf2f6@yadro.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