From: "Christopher Zurcher" <christopher.zurcher@outlook.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"jiewen.yao@intel.com" <jiewen.yao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Lu, Xiaoyu1" <xiaoyu1.lu@intel.com>,
"Jiang, Guomin" <guomin.jiang@intel.com>
Subject: Re: [edk2-devel] CryptoPkg OpensslLib INF files
Date: Fri, 23 Sep 2022 22:39:53 +0000 [thread overview]
Message-ID: <BY3PR06MB8018AAB1717D45E858C992EEE4519@BY3PR06MB8018.namprd06.prod.outlook.com> (raw)
In-Reply-To: <MW4PR11MB587283CCB7236A839AFD7FE18C519@MW4PR11MB5872.namprd11.prod.outlook.com>
I looked at doing this previously and found that depending on the selection of accelerated algorithms (in UefiAsm.conf) you can end up with different sets of non-assembly source files, so that a unified INF would have to contain a copy of the entire Sources section for each architecture target. The build options can also be affected such that you'd have different sets of those as well (the OPENSSL_FLAGS_CONFIG define).
If we can commit to limiting the accelerated algorithms to the current selection, it should be possible to unify the files.
Thanks,
Christopher Zurcher
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Yao, Jiewen
Sent: Friday, September 23, 2022 15:33
To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io; Wang, Jian J <jian.j.wang@intel.com>; Lu, Xiaoyu1 <xiaoyu1.lu@intel.com>; Jiang, Guomin <guomin.jiang@intel.com>
Subject: Re: [edk2-devel] CryptoPkg OpensslLib INF files
Hi Mike
Yes, I agree with you.
If we have a way to reduce the number of INF, we should. Feel free to submit patch.
BTW: Do you think we have chance to combine OpensslLibOpt.inf with OpensslLib.inf, with PCD Feature Flag: "Opt"?
Thank you
Yao Jiewen
> -----Original Message-----
> From: Kinney, Michael D <michael.d.kinney@intel.com>
> Sent: Saturday, September 24, 2022 4:58 AM
> To: devel@edk2.groups.io; Yao, Jiewen <jiewen.yao@intel.com>; Kinney,
> Michael D <michael.d.kinney@intel.com>; Wang, Jian J
> <jian.j.wang@intel.com>; Lu, Xiaoyu1 <xiaoyu1.lu@intel.com>; Jiang,
> Guomin <guomin.jiang@intel.com>
> Subject: CryptoPkg OpensslLib INF files
>
> Hi Jiewen,
>
> I see we now have 6 INF files for the OpensslLib
>
> * OpensslLib.inf
> * OpensslLibCrypto.inf
> * OpensslLibIa32.inf
> * OpensslLibIa32Gcc.inf
> * OpensslLibX64.inf
> * OpensslLibX64Gcc.inf
>
> If I look at the difference between OpensslLib and OpensslLibCrypto,
> the OpensslLibCrypto includes the "ssl" source files.
>
> This looks like a similar problem as the "ec" sources. But the "ec"
> sources were addressed with a PCD FeatureFlag expression so we did not
> have to add another INF.
>
> Could the same technique be applied to the "ssl" sources so we can get
> back to just OpensslLib.inf with an SSL PCD and an EC PCD to
> conditionally build the extra source files?
>
> For the other 4 INF files, these contain the assembly optimized
> algorithms for IA32/X64. I think these 4 INFs can be combined into a single INF.
> Perhaps OpensslLibOpt.inf?
>
> Mike
next prev parent reply other threads:[~2022-09-23 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 20:58 CryptoPkg OpensslLib INF files Michael D Kinney
2022-09-23 22:32 ` Yao, Jiewen
2022-09-23 22:39 ` Christopher Zurcher [this message]
2022-09-24 20:24 ` [edk2-devel] " Michael D Kinney
2022-09-25 17:52 ` Michael D Kinney
2022-09-26 5:46 ` Michael D Kinney
2022-09-26 6:52 ` Christopher Zurcher
2022-09-26 15:40 ` Michael D Kinney
2022-09-26 21:37 ` Christopher Zurcher
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=BY3PR06MB8018AAB1717D45E858C992EEE4519@BY3PR06MB8018.namprd06.prod.outlook.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