From: "Abner Chang" <abner.chang@hpe.com>
To: devel@edk2.groups.io
Cc: Nickle Wang <nickle.wang@hpe.com>, Liming Gao <gaoliming@byosoft.com.cn>
Subject: [PATCH 0/1] Add EDK2 Redfish JSON C Structure stuff into the build
Date: Sat, 14 Aug 2021 11:05:01 +0800 [thread overview]
Message-ID: <20210814030502.3156-1-abner.chang@hpe.com> (raw)
This commit adds below Redfish JSON C Structure stuff into the build,
- edk2 Redfish JSON to C Structure libraries
- edk2 Redfish JSON to C Structure DXE drivers
There are three relevant commits to this one those were not sent for the review
because those are script auto-generated files and too many.
(+18000 files).
1. Redfish JSON schema to C structure source files
https://github.com/changab/edk2-staging/commit/5658ed31ccc9384894a240d5e3c9e06fc785f2cc
2. RedfishClientPkg/Converter: EDK2 Redfish JSON schema to C structure DXE drivers
https://github.com/changab/edk2-staging/commit/8e8497a28947834fa68b62902584f2a1a1fa0205
3.Add EDK2 Redfish JSON C Structure stuff into build
https://github.com/tianocore/edk2-staging/commit/1203c8b185e9071d0bc6222e7d9bf4f5cce9da6b
Above drivers/librares are not all required to be built, only the certain
instances need to be pull in the build process according to the platform demands.
On edk2 Redfish client implementation, only the Redfish schema which referred in
the HII form requires the corresponding EDK2 Redfish JSON C Structure
drivers/libraries to build. This is described in the item #10 in EDK2 Redfish
Client implementation guide at the below link.
https://github.com/tianocore/edk2-staging/blob/edk2-redfish-client/RedfishClientPkg/Readme.md
We also propose to create another Github repo under tianocore for the entire
RedfishClinetPkg. With this we won't add overheads to the regular edk2 repo
because the tons of files.
Signed-off-by: Abner Chang <abner.chang@hpe.com>
Cc: Nickle Wang <nickle.wang@hpe.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Abner Chang (1):
RedfishClientPkg: Add EDK2 Redfish JSON C Structure stuff into build
.../RedfishClientComponents.dsc.inc | 4 +
RedfishClientPkg/RedfishClientDefines.dsc.inc | 7 +
RedfishClientPkg/RedfishClientLibs.dsc.inc | 3 +
.../RedfishJsonStructureDxe.dsc.inc | 2347 +++++++++++++++++
.../RedfishJsonStructureLib.dsc.inc | 2346 ++++++++++++++++
5 files changed, 4707 insertions(+)
create mode 100644 RedfishClientPkg/RedfishJsonStructureDxe.dsc.inc
create mode 100644 RedfishClientPkg/RedfishJsonStructureLib.dsc.inc
--
2.17.1
next reply other threads:[~2021-08-14 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 3:05 Abner Chang [this message]
2021-08-14 3:05 ` [PATCH 1/1] RedfishClientPkg: Add EDK2 Redfish JSON C Structure stuff into build Abner Chang
2021-08-18 7:58 ` [edk2-devel] " Nickle Wang
2021-08-18 14:48 ` Abner Chang
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=20210814030502.3156-1-abner.chang@hpe.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