Hi,
Thank you to everyone who provided feedback. There were no comments against
this proposal, and there was feedback to make some refinements and
clarifications. The detailed proposal with these updates is shown below. We
will start the transition this week. We may need help from the EDK II
community on some of the OS specific scripts to build BaseTools from sources
and scripts to pull BaseTools binaries from
https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/.
Proposed steps:
===============
1) Create new sub-project for BaseTools binaries
a. SVN Link: https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/
b. Status: Done.
2) Intel to provide Build System for BaseTools Win32 binaries
a. SVN Link:
https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32/
b. Build Frequency: Once per day, but only if there are source changes
since last build. Incremental build
c. Build Time: 3 AM PDT
d. Daily builds are incremental. This means that different tool
binaries may have different versions based on the source control system
revision used to perform incremental builds.
e. Clean builds of BaseTools will only be done when a release branch is
created or on-request if there are issues found with incremental build.
d. If build fails for any reason, then build server sends build log to
[email protected] and no new binaries are checked into
https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/.
e. If build succeeds then new binaries are checked into
https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/. A build report in
ReadMe.txt. is checked into the OS specific sub-directory.
f. Initial Build System configuration
############### Build System Information ###############
OS_Name = Windows Server 2008 R2 Enterprise (X64)
OS_Version = 6.1.7601 Service Pack SP1 Build 7601
Visual Studio = Microsoft Visual Studio Team System 2008 Team
Suite SP 1
Python = 2.7.3 (32bit)
cxFreeze = 4.2.3
antlr3 = 3.1.3
McAfee VirusScan Enterprise 8.8
f. Status: In progress. Need a few more validation steps.
3) Delete Win32 binaries from EDK II BaseTools and replace with an SVN extern.
a. Default will continue to pull Win32 binaries
b. Developers that do not want Win32 binaries can opt-out by ignoring
externs.
c. Date: TBD. Goal is immediately after Build System for BaseTools
Win32 binaries is stable.
4) Merge sources from Edk2-buildtools to EDK II BaseTools
a. Date: TBD. Goal is immediately after Build System for BaseTools
Win32 binaries is stable.
5) Change permissions on Edk2-buildtools sub-project to read-only and mark
sub-project as inactive.
a. Date: TBD. Goal is immediately after EDK II BaseTools is synced
with EDK2-buildtools.
6) Retire [email protected] mailing list. All
commits to BaseTools sources will show up on [email protected].
7) Retire [email protected] and move all BaseTools
related discussions to [email protected]
8) Update edksetup.* to optionally build BaseTools from sources or pull
BaseTools binaries from source control
a. edksetup.* detects if binaries are present or not
b. If BaseTools binaries not present, and no flags provided, then
edksetup.* displays help for building BaseTools from sources or pulling
BaseTools binaries from source control if applicable.
c. If binaries not present, and flag to build BaseTools from sources
specified, then build BaseTools from sources.
d. If binaries not present, and flag to pull BaseTools binaries from
source control specified, then use command line source control tools to pull
BaseTools binaries from source control.
e. edksetup.* to support optional flag to specify an alternate
BaseTools binary directory to avoid potential source control system conflicts
with BaseTools\Bin. This would allow a developer to have binaries build by
Build System and locally build binaries present in the same workspace.
f. Date: TBD. Goal is immediately after all tasks above have been
completed. Work on the updates scripts has been started and proposed flags and
details will be shared this week.
g. NOTE: There are additional discussions on binaries from alternate
distribution locations. Edksetup.* may need additional updates/maintenance to
detect and pull from these alternate distribution locations as required.
Thanks,
Mike
-----Original Message-----
From: Kinney, Michael D [mailto:[email protected]]
Sent: Thursday, July 10, 2014 4:12 PM
To: [email protected];
[email protected]
Subject: [edk2-buildtools] [edk2][RFC] Proposal to retire edk2-buildtools
sub-project
Hello,
I am looking for comments on a proposal on how EDK II BaseTools is maintained.
The goal is to move all tool related development activities to the EDK II
BaseTools. This is to address community feedback that there are long delays
between changes made to the edk2-buildtools sub-project and the changes being
propagated to EDK II BaseTools. There has also been feedback that some
developers do not want the overhead of pulling Win32 binaries when they are not
required. I am interested in your feedback (positive or negative) on this
proposal and if you think steps should be added or removed or modified.
I would appreciate feedback by 7/18/2014. Please let us know if you need more
time to evaluate this proposal.
Proposed steps:
===============
1) Create new sub-project for BaseTools binaries
a. SVN Link: https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/
b. Status: Done.
2) Intel to provide build server for BaseTools Win32 binaries
a. SVN Link:
https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32/
b. Build Frequency: Once per day, but only if there are source changes
since last build.
c. Build Time: 3 AM PDT
d. Build server to send email with build log when build is performed.
e. Build server send email that no build was required if no source
changes since last build.
f. Status: In progress. Need a few more validation steps.
3) Delete Win32 binaries from EDK II BaseTools and replace with an SVN extern.
a. Default will continue to pull Win32 binaries
b. Developers that do not want Win32 binaries can opt-out by ignoring
externs.
c. Date: TBD. Goal is immediately after build server is stable.
4) Merge sources from Edk2-buildtools to EDK II BaseTools
a. Date: TBD. Goal is immediately after build server is stable.
5) Change permissions on Edk2-buildtools sub-project to read-only and mark
sub-project as inactive.
a. Date: TBD. Goal is immediately after EDK II BaseTools is synced
with EDK2-buildtools.
6) Retire [email protected] mailing list. All
commits to BaseTools sources will show up on [email protected].
7) Retire [email protected] and move all BaseTools
related discussions to [email protected]
Thanks,
Mike
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
edk2-buildtools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
