From: Laszlo Ersek <lersek@redhat.com>
To: edk2-lists@mc2research.org, edk2-devel@lists.01.org
Subject: Re: Dependency expression inheritance problems
Date: Wed, 28 Mar 2018 20:32:43 +0200 [thread overview]
Message-ID: <51a644fe-dc27-8153-628b-c13bd37970f9@redhat.com> (raw)
In-Reply-To: <000401d3c6c0$aef61660$0ce24320$@mc2research.org>
On 03/28/18 20:14, edk2-lists@mc2research.org wrote:
> Hopefully someone on the list can help with this problem.
>
>
>
> I have a DXE_DRIVER that links with several libraries. Some of these
> libraries are from a binary distribution. I checked the binary library's .INF
> file and it has the [LibraryClasses] and [Depex] sections present in the same
> format as for a source .INF. (not comments)
Isn't that wrong (from the binary distribution)? The INF spec makes me
think think that library instances provided in binary format should ship
their standalone .depex files as well, and they should be referenced in
the [Binaries] section of the respective lib instance INF file.
https://edk2-docs.gitbooks.io/edk-ii-inf-specification/content/2_inf_overview/215_[depex]_section.html#215-depex-section
"Binary .depex files are listed in [Binaries] sections of the INF files."
I vaguely recall seeing an example somewhere, but nothing specific. I
could be totally wrong. :)
Thanks
Laszlo
next prev parent reply other threads:[~2018-03-28 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 18:14 Dependency expression inheritance problems edk2-lists
2018-03-28 18:32 ` Laszlo Ersek [this message]
2018-03-28 18:33 ` Laszlo Ersek
2018-03-28 22:48 ` edk2-lists
2018-03-29 7:07 ` Gao, Liming
2018-03-29 14:52 ` Andrew Fish
2018-03-29 23:10 ` edk2-lists
2018-03-30 0:36 ` Gao, Liming
2018-04-06 22:01 ` darylm
2018-04-06 22:03 ` edk2-lists
2018-04-08 2:03 ` Gao, Liming
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=51a644fe-dc27-8153-628b-c13bd37970f9@redhat.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