Hello Olliver; No objections: sounds like a good plan.
Just to let you know: - I created an ooo-dmake port on Google Code that has been moved to Apache-Extras as "dmake". - On LO FreeBSD's port they set $DMAKE in the configure environment and use the external dmake. cheers, Pedro. --- On Fri, 11/4/11, Oliver-Rainer Wittmann <[email protected]> wrote: > From: Oliver-Rainer Wittmann <[email protected]> > Subject: [code] main/dmake > To: [email protected] > Date: Friday, November 4, 2011, 10:38 AM > 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. >
