public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io, bob.c.feng@intel.com
Cc: "Gao, Liming" <gaoliming@byosoft.com.cn>,
	"Chen, Christine" <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: Thu, 22 Sep 2022 21:42:53 -0700	[thread overview]
Message-ID: <9f0d7130-d4a8-ec8f-9b54-dd757d6a5fbe@gmail.com> (raw)
In-Reply-To: <PH7PR11MB586349EFE26ABC3F77C8811BC94E9@PH7PR11MB5863.namprd11.prod.outlook.com>

Thanks for the help, Bob. It seems that one of the "Reviewed-by" tags 
are breaking the pipeline patchcheck: 
https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=62531&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=9c939e41-62c2-5605-5e05-fc3554afc9f5

Would like me to send a v2 patch?

Regards,
Kun

On 09/22/2022 04:26, Bob Feng wrote:
> Create PR https://github.com/tianocore/edk2/pull/3378 for merge.
> 
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Bob Feng
> Sent: Thursday, September 22, 2022 7:11 PM
> To: Kun Qin <kuqin12@gmail.com>; devel@edk2.groups.io
> Cc: Gao, Liming <gaoliming@byosoft.com.cn>; Chen, Christine <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
> 
> Reviewed-by: Bob Feng <bob.c.feng@intel.com>
> 
> -----Original Message-----
> From: Kun Qin <kuqin12@gmail.com>
> Sent: Thursday, September 22, 2022 4:45 AM
> To: devel@edk2.groups.io
> Cc: Feng, Bob C <bob.c.feng@intel.com>; Gao, Liming <gaoliming@byosoft.com.cn>; Chen, Christine <yuwei.chen@intel.com>; Sean Brogan <sean.brogan@microsoft.com>
> Subject: [PATCH v1 1/1] BaseTools: Edk2ToolsBuild: Fixing pipeline build due to path too long
> 
> 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]) --
> 2.37.1.windows.1
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

      reply	other threads:[~2022-09-23  4:42 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   ` [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 [this message]

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=9f0d7130-d4a8-ec8f-9b54-dd757d6a5fbe@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