Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of r.bircher@gmx.ch designates
 213.165.64.22 as permitted sender)
Message-ID: <4EB464EE.4050007@gmx.ch>
Date: Fri, 04 Nov 2011 23:19:26 +0100
From: Raphael Bircher <r.bircher@gmx.ch>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: [code] main/dmake
References: <4EB406F8.6020909@googlemail.com>
In-Reply-To: <4EB406F8.6020909@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Am 04.11.11 16:38, schrieb Oliver-Rainer Wittmann:
> 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.
This looks good for me. A other Idea would be to put this in the 
ext_sources. We hav allready this directory. Simply as imput.

Greetings Raphael

-- 
My private Homepage: http://www.raphaelbircher.ch/