From: "Christian Rodriguez" <christian.rodriguez@intel.com>
To: Christian Rodriguez <christian.rodriguez@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [Patch V3] OpensslLib: Missing local header files in [Sources] section of .INFs
Date: Thu, 06 Jun 2019 13:00:52 -0700 [thread overview]
Message-ID: <3911.1559851252162883232@groups.io> (raw)
In-Reply-To: <20190521211215.13452-1-christian.rodriguez@intel.com>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Hi Xiaoyu,
For your comment (1), I don't see a way to rule out headers using configdata. I was already using configdata to get the include directories, but configdata doesn't list the specific header files that will be used for compilation.
We can ignore things with a common name or specific files, but ruling out all of them doesn't seem possible using what is given.
The rest of the comments can be addressed.
[-- Attachment #2: Type: text/html, Size: 447 bytes --]
prev parent reply other threads:[~2019-06-06 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 21:12 [Patch V3] OpensslLib: Missing local header files in [Sources] section of .INFs Christian Rodriguez
2019-05-22 9:40 ` [edk2-devel] " Xiaoyu Lu
2019-05-22 9:49 ` Laszlo Ersek
2019-05-22 14:14 ` Christian Rodriguez
2019-06-06 20:00 ` Christian Rodriguez [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=3911.1559851252162883232@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