Tim, I see this as more immediately usable. I now only have to pull and monitor a single repo that already has all the source for the build tools. I can also easily checkout a release branch and build the matching tools for that version of UDK. It also simplifies debugging and development of tools. I also like the fact that I can update python to include the latest security patches as needed.
To help with the process on Windows edksetup.bat has the ability to build the tools using the Rebuild and ForceRebuild options. Thanks, -Erik -----Original Message----- From: af...@apple.com [mailto:af...@apple.com] Sent: Thursday, March 8, 2018 10:37 AM To: Tim Lewis <tim.le...@insyde.com> Cc: Bjorge, Erik C <erik.c.bjo...@intel.com>; edk2-devel@lists.01.org Subject: Re: [edk2] RFC: Proposal to halt automatic builds of Windows BaseTools executables > On Mar 8, 2018, at 10:05 AM, Tim Lewis <tim.le...@insyde.com> 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 <edk2-devel-boun...@lists.01.org> On Behalf Of > Bjorge, Erik C > Sent: Wednesday, March 7, 2018 9:57 AM > To: edk2-devel@lists.01.org > 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 > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
