From: "Joey Vagedes via groups.io" <joeyvagedes=microsoft.com@groups.io>
To: Aleksey Ryzhov <a.ryzhov@yadro.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] Some unpredictable behavior while parsing the FDF file.
Date: Thu, 28 Dec 2023 08:09:34 -0800 [thread overview]
Message-ID: <26170.1703779774175995343@groups.io> (raw)
In-Reply-To: <7b4101c435f24cf6aed865b7040bf2f6@yadro.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Hello.
It depends on the actual path that you are trying to include. This is the requirements for an include statement (coming directly from the FDF specification):
>
>
>
> The tools look for <Filename> relative to the directory the FDF file
> resides. If the file is not found, and the directory containing this FDF
> file is not the same directory as the directory containing the DSC file,
> the tools must attempt to locate the file relaitive to the directory that
> contains the DSC file.
>
>
>
> If none of these methods find the file, and a directory separator is in <Filename>
> , the tools attempt to find the file in a WORKSPACE (or a directory listed
> in the PACKAGES_PATH) relative path. If the file cannot be found, the
> build system must exit with an appropriate error message.
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112984): https://edk2.groups.io/g/devel/message/112984
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: 2804 bytes --]
prev parent reply other threads:[~2023-12-28 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 20:10 [edk2-devel] Some unpredictable behavior while parsing the FDF file Aleksey Ryzhov
2023-12-28 16:09 ` Joey Vagedes via groups.io [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=26170.1703779774175995343@groups.io \
--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