public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: <devel@edk2.groups.io>, Leif Lindholm <quic_llindhol@quicinc.com>,
	"Michael Kinney" <michael.d.kinney@intel.com>,
	Andrew Fish <afish@apple.com>,
	"Michael Kubacki" <mikuback@linux.microsoft.com>,
	Sean Brogan <sean.brogan@microsoft.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Pip edk2-basetools diverged from edk2/BaseTools (e.g. doesn't have "Revert "BaseTools: Fix DSC LibraryClass precedence rule"")
Date: Wed, 7 Sep 2022 07:08:00 -0600	[thread overview]
Message-ID: <d9a0ee15-c2a9-f95f-32c2-cc8a28477ba6@quicinc.com> (raw)

I've been running into a problem with CI that was fixed in edk2 BaseTools before the recent stable tag:


ERROR - Compiler #3000 from 
/home/vsts/work/1/s/MdeModulePkg/Library/SmmLockBoxLib/SmmLockBoxPeiLib.inf(42): 
PCD [gEfiMdeModulePkgTokenSpaceGuid.PcdDxeIplSwitchToLongMode] in 
[/home/vsts/work/1/s/MdeModulePkg/Library/SmmLockBoxLib/SmmLockBoxPeiLib.inf] 
is not found in dependent packages:

I noticed that CI is using the Pip based tools, and from comparing 
https://github.com/tianocore/edk2-basetools/commits/master and 
https://github.com/tianocore/edk2/commits/master/BaseTools it's clear 
they've diverged, and the former for example doesn't have "Revert 
"BaseTools: Fix DSC LibraryClass precedence rule"", as well as several 
other fixes.

Could we get them synced up?

-- 
Rebecca Cran

             reply	other threads:[~2022-09-07 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:08 Rebecca Cran [this message]
2022-09-07 14:52 ` [edk2-devel] Pip edk2-basetools diverged from edk2/BaseTools (e.g. doesn't have "Revert "BaseTools: Fix DSC LibraryClass precedence rule"") Bob Feng

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=d9a0ee15-c2a9-f95f-32c2-cc8a28477ba6@quicinc.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