Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <4F0EB885.8030201@a-w-f.de>
References: <4F0EB885.8030201@a-w-f.de>
Date: Thu, 12 Jan 2012 08:19:22 -0500
Message-ID: 
 <CAP-ksoijk+-SZb5w2EmAM5QZt=R8TqXuHB_4dxo+QwRbY6_WKQ@mail.gmail.com>
Subject: Re: External libraries
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 12, 2012 at 5:40 AM, Andre Fischer <af@a-w-f.de> wrote:
> Hi all,
>
> During the work on replacing lp_solve with CoinMP (almost done) I stumble=
d
> 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/. =C2=A0By reusing s=
ome of
> the old source_config functionality (in the form of the SourceConfig.pm i=
n
> solver/bin/modules) the new modules in ext_libraries/ (coinmp in my examp=
le)
> can be transparently integrated into the build process.
>
> My plan is to add the ext_sources/ directory and integrate it into our bu=
ild
> system and then to add modules for coinmp and, when the need arises, for
> other new external libraries. =C2=A0Existing modules in main/, like moz o=
r cairo,
> can be moved later.
>
> Any comments, objections, questions for more information?
>

What is the difference then between ext_sources and ext_libraries?
How do you decide which goes where?

> Regards,
> Andre