Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jogischmidt@googlemail.com
 designates 74.125.83.47 as permitted sender)
Message-ID: <4F0EBC38.4030309@googlemail.com>
Date: Thu, 12 Jan 2012 11:55:52 +0100
From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= <jogischmidt@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: External libraries
References: <4F0EB885.8030201@a-w-f.de>
In-Reply-To: <4F0EB885.8030201@a-w-f.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/12/12 11:40 AM, Andre Fischer wrote:
> Hi all,
>
> During the work on replacing lp_solve with CoinMP (almost done) I
> stumbled upon the question of where to build the CoinMP libraries.
>
> Following the current pattern I would add a coinmp directory into main/
> The downside of this is that the main/ directory becomes cluttered with
> modules that basically consist only of a single makefile and maybe some
> patch files.
>
> I would like to propose a different solution: add a new ext_libraries/
> directory at the same level of main/ and ext_sources/. By reusing some
> of the old source_config functionality (in the form of the
> SourceConfig.pm in solver/bin/modules) the new modules in ext_libraries/
> (coinmp in my example) can be transparently integrated into the build
> process.
>
> My plan is to add the ext_sources/ directory and integrate it into our
> build system and then to add modules for coinmp and, when the need
> arises, for other new external libraries. Existing modules in main/,
> like moz or cairo, can be moved later.
>
> Any comments, objections, questions for more information?

+1 sounds like a very good idea to cleanup the source tree further and 
make the strucutre more intuitive (at least for me)

Juergen