On 15.10.2013 10:45, janI wrote:
On 15 October 2013 10:02, Andre Fischer <awf....@gmail.com> wrote:
Some time ago I have written a Perl script that basically what Jan has
outlined. It reads the build.lst files and creates one Makefile that calls
dmake and GNU make for the projects.
The only problem with this aproach, and the reason why I did not finalized
this experiment, is that build.pl has a lot of other features and options
besides the regular build. Understanding these and replicating them is the
hard part.
I would not mind having a copy of the script if possible ?
Sure. You can find it here:
http://people.apache.org/~af/build.zip
There is a readme (which I called index.html for reasons that I can't
remember). Its "How to use" section explains, well, how to use the
script and the makefile it creates. But I don't know if it still works
properly.
I think we need a big discussion to whether a new system should support all
options and features of the existing systems.
We should definitely remove any options that where added over the years
but are not used anymore. But it might be good to first understand
which options there really are and what "not used anymore" means.
There may be functionality that is used only once every six months when
a release is built. But maybe such functionality can be moved to its
own script.
As an example, we remove most (if not all) options in configure by having
an option like "--generate_platform=xyz" where xyz is one of our supported
release platforms. The --generate-platform would internally set the same
options we use to generate the releases.
Going in such a direction will of course limit the build variations, but I
am not sure if that is a bad thing ?
Certainly not.
-Andre
rgds
jan I.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
