public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pete Batard via groups.io" <pete=akeo.ie@groups.io>
To: devel@edk2.groups.io, jiewen.yao@intel.com, "Kinney,
	Michael D" <michael.d.kinney@intel.com>,
	"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] libspdm Breaking Builds
Date: Wed, 29 May 2024 19:17:57 +0100	[thread overview]
Message-ID: <f0dcee54-a31c-4f04-baa4-c1ea63364897@akeo.ie> (raw)
In-Reply-To: <MW4PR11MB5872635881E2E5CCD37985748CF52@MW4PR11MB5872.namprd11.prod.outlook.com>

Hello all,

On 2024.05.24 03:13, Yao, Jiewen via groups.io wrote:
> Please let us know if the preference for libspdm submodule. (Below options)
> 1) Keep current libspdm official 3.3.0 release, and update to next release at the beginning of July.
> 2) Update libspdm immediately with the new cmocka submodule, which is NOT an official release.

Considering that I (and I expect anybody who tries to use EDK2 as a 
submodule in their UEFI build projects with GitHub Actions), I have to 
vote for option 2.

An example of the current issue can be shown on a project that simply 
attempts to build the UEFI Shell from the latest stable EDK2 release, 
using EDK2 as a submodule, can be shown at 
https://github.com/pbatard/UEFI-Shell/actions/runs/9290685065/job/25567879807 
or 
https://github.com/pbatard/UEFI-Shell/actions/runs/9290988138/job/25568511355 
and as you can see, it makes building the project completely impossible 
unless you ditch using EDK2 as a submodule (which isn't a viable option 
IMO, because a build toolchain that cannot be used as a git submodule is 
a very limiting toolchain).

For information, there's only so much fine grained tuning GitHub Actions 
offers on submodules, and no matter how you try to play with the fetch 
depth, the fact that one of the libspdm sub-dependency has essentially 
become M.I.A. is something that should be addressed as a matter of urgency.

So I hope that a commit that updates libspdm to the new cmocka submodule 
can find its way into EDK2 fairly soon, as it is currently halting a 
projects that aims at producing trusted UEFI Shell releases.

Regards,

/Pete


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119358): https://edk2.groups.io/g/devel/message/119358
Mute This Topic: https://groups.io/mt/106250971/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-05-29 18:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 20:40 [edk2-devel] libspdm Breaking Builds Michael Kubacki
2024-05-22 21:57 ` Michael D Kinney
2024-05-22 22:16   ` Michael Kubacki
2024-05-22 22:24     ` Michael D Kinney
2024-05-23  1:04       ` Michael Kubacki
2024-05-23  1:51         ` Michael D Kinney
2024-05-23  2:16           ` Yao, Jiewen
     [not found]           ` <17D1FC93E885E03F.15878@groups.io>
2024-05-24  2:13             ` Yao, Jiewen
2024-05-29 18:17               ` Pete Batard via groups.io [this message]
2024-05-29 18:33                 ` Michael D Kinney
2024-05-29 19:40                   ` Michael D Kinney
2024-05-29 19:57                     ` Michael Kubacki
2024-05-30  0:31                       ` Yao, Jiewen
2024-05-29 22:00                     ` Pete Batard via groups.io
2024-05-30  0:32                       ` Michael D Kinney

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=f0dcee54-a31c-4f04-baa4-c1ea63364897@akeo.ie \
    --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