> On Mar 8, 2018, at 10:05 AM, Tim Lewis <[email protected]> wrote:
> 
> Erik --
> 
> What is the justification? Moving from more immediately usable to less
> immediately usable doesn't seem, on the surface, to be  a good direction.
> Why not go the other direction and pre-build the binaries for the other
> environments?
> 

Tim,

I'm not a big fan of the prebuilt tools. In a production environment it is 
usually preferable to have source and to NOT check in binaries. Given the other 
environments have Python by default I don't see the value of pre-building the 
tools on Unix systems? 

I think the ease of use issue is really a different issue (other than having to 
install Python).  Most projects you start from the root and type make (nmake). 
A top level makefile would abstract the building of the tools and the need to 
setup environment variables. 

Why can't I pull a git repo and do:
$ make OvmfPkgX64

I grant it may be hard to automagically pick the compiler but you can do things 
like:
$ make OvmfPkgX64 BUILD_FLAGS="-n 1 -t XCODE"

As long as build.py acts like a compiler and the last version of a given flag 
wins this should be easy to do. 

Thanks,

Andrew Fish

> Thanks,
> 
> Tim
> 
> -----Original Message-----
> From: edk2-devel <[email protected]> On Behalf Of Bjorge, Erik
> C
> Sent: Wednesday, March 7, 2018 9:57 AM
> To: [email protected]
> Subject: [edk2] RFC: Proposal to halt automatic builds of Windows BaseTools
> executables
> 
> I would like to propose that the automatic builds of Windows BaseTools
> executables be halted.  This implies there will no longer be updates to the
> edk2-BaseTools-win32 repository.
> 
> With this change, developers using Windows must install Python 2.7.x and
> configure their environment to build C tools  and run python scripts from
> sources.  This matches the development experience for non-Windows
> environments.
> 
> Please respond with comments by 03/23/2018.
> 
> Thanks,
> -Erik
> 
> _______________________________________________
> edk2-devel mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/edk2-devel
> 
> _______________________________________________
> edk2-devel mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/edk2-devel

_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to