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: setup and C++ STL X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Fri, 12 Apr 2002 16:08:10 +1000 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 g3C68sC13051 I'd like to remove some of the hoemgrown templates, and/or turn them into extensions to the STL. String++ for example would likely be better as a has-a combined with Unicode support and FormatMessage support. This needs (IIRC) several things: 1) The cross-compiling all-in-one-run tree that builds i686-pc-cygwin-gcc, libgcc etc needs to be altered so that it builds both a cygwin libgcc and a mingw libgcc. 2) The STL needs to be included in that tree if it's not already, and it needs to be added to the cinstall Makefile search path. 3) Anything else that cgf adds after he reads my email. I don't have time to do 1) or the first half of 2). Any volunteers? There are some side-benefits to this. 1) It would allow a mingw libgcc to be built easily, making a package of that a potential reality. 2) cinstall would get YA template overhaul. 3) Folk sending patches to cinstall would find the source base more easily understood (if they have STL background). Rob