Hi Sean,
That the Basetools works correctly depends on the PACAKGES_PATH is set correctly. I think this patch provides common function and provides assistance for the Basetools.
Thanks,
Bob
From: Ni, Ray
Sent: Tuesday, April 7, 2020 10:16 AM
To: devel@edk2.groups.io; sean.brogan@microsoft.com; Luo, Heng <heng.luo@intel.com>
Cc: Feng, Bob C <bob.c.feng@intel.com>
Subject: RE: [edk2-devel] [PATCH] BaseTools/Scripts: Add scripts to set PACKAGES_PATH environment
Sean,
PyTools is good. This patch is to support those platforms that haven’t adopted PyTools for their platform build.
Thanks,
Ray
From: devel@edk2.groups.io <devel@edk2.groups.io>
On Behalf Of Sean via groups.io
Sent: Thursday, April 2, 2020 11:59 PM
To: Luo, Heng <heng.luo@intel.com>;
devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH] BaseTools/Scripts: Add scripts to set PACKAGES_PATH environment
I am not a fan of this. The community and design meetings have had a few discussions about tools (PyTools has been presented twice) and a few brief discussions about common patterns to build platforms but I don't think there is real alignment.
Each "platform" has its own way of doing things.
As for this patch, I don't really want to see a bunch of scripts added to edk2 basetools that are not aligned with a community agreed direction (or any clear direction). It has also been brought up that basetools as a python package/project is a challenge
to work with and has some fundamental problems. Adding more in a similar design pattern is not how we start fixing it. As an example for edk2-pytools, an RFC was offered and even then it was added as its own repositories to avoid more directly to the edk2
repo.
@Mike K - Any progress on getting a tools subtream setup? Any governance ideas to help align these efforts.
Thanks
Sean