Hi,
I have a first version ready that works like outlined before. Details
and the patch can be found in issue 108604
(https://issues.apache.org/ooo/show_bug.cgi?id=118604).
I did not yet remove the internal dmake source code, yet. I would like
to have the downloading and building better tested before removing it.
Having no functioning dmake executable would be a very severe build breaker.
I tested this on Windows and Linux with the source code package provided
by Pedro (can be found at
http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2)
but I need help to test this more thoroughly. So, please apply the
patch and play around with the --with-dmake-path and --with-dmake-url
options.
Best regards,
Andre
On 04.11.2011 16:38, Oliver-Rainer Wittmann wrote:
Hi,
our build tool dmake is licensed under GPL.
Thus, it can not be part of our source releases.
But, we can use it for building - as we are using the gcc compiler.
Thus, I will move the dmake source folder from .../ooo/trunk/main/ to
new folder .../ooo/buildtools/ in order to assure that everything under
.../ooo/trunk/ can become part of our source release.
In order to get our bootstrap process still working it needs some adaption:
I am planning to introduce a configure option in order to provide
manually the path to the source folder of the build tool dmake -
something like with-dmake=<$PATH to dmake folder>. If this option is not
used, the default path ../../buildtools/dmake/ - relative from folder
main - will be taken. The configure will then check, if this folder
exists - the manual given one or the default. The bootstrap process will
then work with this path to create the build tool dmake.
Any objections?
Best regards, Oliver.