From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.100; helo=mga07.intel.com; envelope-from=erik.c.bjorge@intel.com; receiver=edk2-devel@lists.01.org Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9AC6722568619 for ; Thu, 8 Mar 2018 11:46:11 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2018 11:52:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,442,1515484800"; d="scan'208";a="24075190" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by orsmga006.jf.intel.com with ESMTP; 08 Mar 2018 11:52:27 -0800 Received: from orsmsx154.amr.corp.intel.com (10.22.226.12) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 8 Mar 2018 11:52:27 -0800 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.126]) by ORSMSX154.amr.corp.intel.com ([169.254.11.77]) with mapi id 14.03.0319.002; Thu, 8 Mar 2018 11:52:27 -0800 From: "Bjorge, Erik C" To: "afish@apple.com" , Tim Lewis CC: "edk2-devel@lists.01.org" Thread-Topic: [edk2] RFC: Proposal to halt automatic builds of Windows BaseTools executables Thread-Index: AdO2PXuIaQsBYeABTfaRaBufreN5DwBDZYWAAAEeQQAAEHkgYA== Date: Thu, 8 Mar 2018 19:52:26 +0000 Message-ID: <7FE3244EBB31F1449E4EC79CFE44E3F4ACA8FE9D@ORSMSX114.amr.corp.intel.com> References: <7FE3244EBB31F1449E4EC79CFE44E3F4ACA8ED8F@ORSMSX114.amr.corp.intel.com> <00ef01d3b708$059e05e0$10da11a0$@insyde.com> <714C59A1-275B-4090-955D-F135B6E70DD1@apple.com> In-Reply-To: <714C59A1-275B-4090-955D-F135B6E70DD1@apple.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjQ2NGU3NTYtZDJlYi00MDAyLTg5ZWYtY2EzNTAwNjE5ZDRmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlRJS0hBcjN0WVhkMGdYRnQ3Q2VDXC9RS3dcL09wcUhYRGtoa0tiTDdGUVwvQlU9In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Subject: Re: RFC: Proposal to halt automatic builds of Windows BaseTools executables X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 19:46:12 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 t= he tools using the Rebuild and ForceRebuild options. Thanks, -Erik =20 -----Original Message----- From: afish@apple.com [mailto:afish@apple.com]=20 Sent: Thursday, March 8, 2018 10:37 AM To: Tim Lewis Cc: Bjorge, Erik C ; edk2-devel@lists.01.org Subject: Re: [edk2] RFC: Proposal to halt automatic builds of Windows BaseT= ools executables > On Mar 8, 2018, at 10:05 AM, Tim Lewis wrote: >=20 > Erik -- >=20 > What is the justification? Moving from more immediately usable to less=20 > 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=20 > other environments? >=20 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 o= ther environments have Python by default I don't see the value of pre-build= ing the tools on Unix systems?=20 I think the ease of use issue is really a different issue (other than havin= g 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.=20 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 th= ings like: $ make OvmfPkgX64 BUILD_FLAGS=3D"-n 1 -t XCODE" As long as build.py acts like a compiler and the last version of a given fl= ag wins this should be easy to do.=20 Thanks, Andrew Fish > Thanks, >=20 > Tim >=20 > -----Original Message----- > From: edk2-devel On Behalf Of=20 > 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=20 > BaseTools executables >=20 > I would like to propose that the automatic builds of Windows BaseTools=20 > executables be halted. This implies there will no longer be updates=20 > to the > edk2-BaseTools-win32 repository. >=20 > With this change, developers using Windows must install Python 2.7.x=20 > and configure their environment to build C tools and run python=20 > scripts from sources. This matches the development experience for=20 > non-Windows environments. >=20 > Please respond with comments by 03/23/2018. >=20 > Thanks, > -Erik >=20 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel >=20 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel