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
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: RFP: boost libraries
Date: Sun, 5 May 2002 00:43:53 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5FBE@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: "David Abrahams" <david DOT abrahams AT rcn DOT com>,
   "Jason Tishler" <jason AT tishler DOT net>, <boost AT lists DOT boost DOT org>
Cc: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g44Ehwo15952



> -----Original Message-----
> From: David Abrahams [mailto:david DOT abrahams AT rcn DOT com] 
> Sent: Friday, May 03, 2002 12:11 AM

> * Most of these libraries are just C++ templates in header files

Ah. I wasn't aware of that. Just dumb luck I guess - picking the regex
library, which does have a .a component, and a .so - but no .dll.
 

> * There is already a DLL version of the Boost.Regex and 
> Python libs (the static lib version of Boost.Python is 
> available but deprecated).

Where does one find the Regex dllized lib?
 
> * Nobody has decided what an appropriate unix-style 
> installation for boost would look like (where the headers 
> live, how the libs should be named and versioned, what 
> symlinks to make, etc.). We need guidance on this. Normally 
> we tell people to download the boost tree, put the root in 
> their #include path, build the libraries, manually collect 
> them and put them wherever they want. There has been 
> increasing dissatisfaction with this approach.

Right. Uhmm, I think that debian makes the boost libraries available,
chances are that the packager there has found a good solution, or the
package would have failed there package linter.
 
I can (and will, but in no great hurry) look into that aspect a little
if you like.

Rob