This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
RE: RFP: boost libraries
- 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>
- Date: Sun, 5 May 2002 00:43:53 +1000
- Subject: RE: RFP: boost libraries
> -----Original Message-----
> From: David Abrahams [mailto:david.abrahams@rcn.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