From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io
Cc: Bob Feng <bob.c.feng@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Yuwei Chen <yuwei.chen@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: [PATCH v1 0/1] Fixing BaseTool build break
Date: Wed, 21 Sep 2022 13:44:58 -0700 [thread overview]
Message-ID: <20220921204459.821-1-kuqin12@gmail.com> (raw)
Currently the BaseTool build step is failing and caused the pipeline to
malfunciton.
The issue is due to the environment path too long during the build
process and adding VC toolchain path to the environment variable will
fail due to Windows varaible length limit.
Patch v1 branch: https://github.com/kuqin12/edk2/tree/fix_edk2_build
Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Yuwei Chen <yuwei.chen@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Sean Brogan (1):
BaseTools: Edk2ToolsBuild: Fixing pipeline build due to path too long
BaseTools/Edk2ToolsBuild.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.37.1.windows.1
next reply other threads:[~2022-09-21 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 20:44 Kun Qin [this message]
2022-09-21 20:44 ` [PATCH v1 1/1] BaseTools: Edk2ToolsBuild: Fixing pipeline build due to path too long Kun Qin
2022-09-21 23:09 ` [edk2-devel] " Sean
2022-09-22 11:11 ` Bob Feng
[not found] ` <17172A4739518A26.13460@groups.io>
2022-09-22 11:26 ` [edk2-devel] " Bob Feng
2022-09-23 4:42 ` Kun Qin
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=20220921204459.821-1-kuqin12@gmail.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