From: "Rebecca Cran" <rebecca@bsdio.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Michael Kubacki <mikuback@linux.microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Subject: OvmfPkg PlatformCI: Should iasl dependency be updated from 20190215.0.0 ?
Date: Wed, 3 May 2023 13:34:48 -0600 [thread overview]
Message-ID: <5970efe0-b520-f92d-db2f-6ed809ce4e55@bsdio.com> (raw)
I noticed OvmfPkg/PlatformCI/iasl_ext_dep.yaml specifies iasl version
20190215.0.0 while BaseTools/Bin/iasl_ext_dep.yaml has the newer
20200717.0.0, and "mono .../edk2toolext/bin/NuGet.exe list -Source
https://pkgs.dev.azure.com/projectmu/acpica/_packaging/mu_iasl/nuget/v3/index.json"
shows there's version 20210105.0.6 available.
Though OvmfPkg is using source https://api.nuget.org/v3/index.json while
BaseTools uses
https://pkgs.dev.azure.com/projectmu/acpica/_packaging/mu_iasl/nuget/v3/index.json
- I don't know why they're different.
I was wondering if iasl_ext_dep.yaml should be updated?
Also, the example in
https://github.com/tianocore/tianocore.github.io/wiki/How-to-Build-With-Stuart
of using stuart_build to build OVMF seems to be missing a step: running
"stuart_update -c PlatformBuild.py TOOL_CHAIN_TAG=GCC5 -a X64" appears
to be required otherwise stuart_build will complain that the iasl
dependency hasn't been met.
--
Rebecca Cran
next reply other threads:[~2023-05-03 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 19:34 Rebecca Cran [this message]
2023-05-03 19:50 ` [edk2-devel] OvmfPkg PlatformCI: Should iasl dependency be updated from 20190215.0.0 ? Sean
2023-05-03 20:06 ` Rebecca Cran
2023-05-04 5:56 ` Gerd Hoffmann
2023-05-05 3:13 ` Sean
2023-05-04 17:21 ` Michael D Kinney
2023-05-05 2:17 ` Michael Kubacki
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=5970efe0-b520-f92d-db2f-6ed809ce4e55@bsdio.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