Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
Subject: attn cgf - single build integration
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Sat, 20 Apr 2002 09:49:34 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5E8A@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Cygwin-Apps" <cygwin-apps AT sources DOT redhat DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3JNo3x14021

Chris,
	I'm approaching a point with libgetopt++ that I'll want to roll
it into setup. This will (obviously) affect the single-build procress,
so I'm hoping that you can confirm or suggest alterations to my plan:

I think that as a general purpose library, it should sit at
winsup/libgetopt++ or even a level above. However the binary linked into
setup.exe needs to be built knowing about setup's String class (as
opposed to the C++ standard basic_string).

So here's my idea:
we put the library at winsup/libgetopt++ 
we make a symlink in the source tree at cinstall/libgetopt++ to
../libgetopt++

During configure time setup sub-configures libgetopt++ as a static only
library in cinstall/libgetopt++

In the future if any other programs want to start using it, we make
winsup subconfigure winsup/libgetopt++.

What do you think?

Rob