public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, kuqin12@gmail.com
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: Re: [edk2-devel] [PATCH v1 1/1] BaseTools: Edk2ToolsBuild: Fixing pipeline build due to path too long
Date: Wed, 21 Sep 2022 16:09:39 -0700	[thread overview]
Message-ID: <BY3PR19MB49009FEBA09E3AAA7912BC9CC84F9@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20220921204459.821-2-kuqin12@gmail.com>

Reviewed-by:  Sean Brogan <sean.brogan@microsoft.com>


On 9/21/2022 1:44 PM, Kun Qin wrote:
> From: Sean Brogan <sean.brogan@microsoft.com>
>
> Current implementation of looking up toolchain will _insert_ the findings
> from vsvarsall.bat to existing path and potentially stuff the variable to
> exceed the length of maximal path length accepted by Windows.
>
> This change updated the logic to use the discovered shell varialbes to
> replace the existing path, which is desirable in the specific use case.
>
> Cc: Bob Feng <bob.c.feng@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Yuwei Chen <yuwei.chen@intel.com>
>
> Co-authored-by: Sean Brogan <sean.brogan@microsoft.com>
> Signed-off-by: Kun Qin <kuqin12@gmail.com>
> ---
>   BaseTools/Edk2ToolsBuild.py | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/BaseTools/Edk2ToolsBuild.py b/BaseTools/Edk2ToolsBuild.py
> index 1ea8187de693..f862468ce275 100644
> --- a/BaseTools/Edk2ToolsBuild.py
> +++ b/BaseTools/Edk2ToolsBuild.py
> @@ -122,7 +122,7 @@ class Edk2ToolsBuild(BaseAbstractInvocable):
>               for key in vc_vars.keys():
>
>                   logging.debug(f"Var - {key} = {vc_vars[key]}")
>
>                   if key.lower() == 'path':
>
> -                    shell_env.insert_path(vc_vars[key])
>
> +                    shell_env.set_path(vc_vars[key])
>
>                   else:
>
>                       shell_env.set_shell_var(key, vc_vars[key])
>
>   
>

  reply	other threads:[~2022-09-21 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 20:44 [PATCH v1 0/1] Fixing BaseTool build break Kun Qin
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   ` Sean [this message]
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=BY3PR19MB49009FEBA09E3AAA7912BC9CC84F9@BY3PR19MB4900.namprd19.prod.outlook.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