Sorry for top posting. There seems to be some confusion, about the project.
The goal is not to replace the current system (this is only a potential long time goal). The goal is to make a parallel build system suited for windows developers, and then in a second phase generate makefiles for linux. In the beginning of this thread I posted information, which is repeated below: ====== Project SVN Branch: https://svn.apache.org/repos/asf/openoffice/branches/capstone2013 Motivation AOO’s current build system is old, non-standard, hard to understand, and undocumented. To attract new developers, Apache Software Foundation would like to create a new/modern build system. Objectives 1. Develop a build system for Microsoft Visual Studio (Windows), and Linux. Focus on making Windows development easy. 2. Implement the new build system in parallel with the current build system. 3. Help test the new new build system. Deliverables 1. “How to” report before programming. 2. In June, a build system capable of generating AOO in Windows and in Linux =============== I have also made a wiki page (also published earlier): http://wiki.openoffice.org/wiki/Build_System_Analysis:capstone2013_windows_build I encourage everyone to participate in the discussions. rgds jan I. On 14 October 2013 09:26, Andre Fischer <awf....@gmail.com> wrote: > On 12.10.2013 23:33, Dave Fisher wrote: > >> Perhaps you will unlock the path to a digitally signed build for Windows. >> That would be huge! >> >> I don't think that that is a shortcoming of the build system (which has > many). It is more a restriction on the administrative side of OpenOffice > and Apache. > > -Andre > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org<dev-unsubscr...@openoffice.apache.org> > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
