Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , 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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: attn cgf - single build integration Date: Sat, 27 Apr 2002 11:19:27 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3R1JZ624028 > -----Original Message----- > From: Robert Collins > Sent: Saturday, April 20, 2002 9:50 AM > To: Cygwin-Apps > Subject: attn cgf - single build integration > > > 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? With setup moved, there is no current requirement to put libgetopt++ in the winsup tree, so I won't be doing the above. Of course, it's such a great library it should be there :}. Rob