X-Spam-Check-By: sourceware.org
Message-ID: <43D2D591.D2F47457@dessent.net>
Date: Sat, 21 Jan 2006 16:45:05 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: boost library suggestion (regarding boost::filesystem)
References: <dquimc$jjt$1 AT sea DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Simon Lam wrote:

> I'd like to suggest that the boost library is built as the gcc-nocygwin
> toolset (which, if I have read the docs correctly, is just an extension
> of the gcc toolset) or make available as a seperate package. The reason
> behind this is that part of the library, boost::filesystem, do not work
> as intended. The library, under the current cygwin build, thinks that
> the native path format is *nix style (/usr/blahblah), but correctly it
> should be windows format (c:\blahblah).

This is the Cygwin project, not the mingw project.  Apps and libraries
are expected to use posix paths (/usr/bin/whatever) and it would be
incorrect for them to try to use native paths.

If you want a Boost that doesn't use posix filenames, then build it
yourself and offer to maintain it for the mingw project.  But that's not
relevant here, because the whole aim of Cygwin is to provide a posix
environment.  All the packages offered in the Cygwin distro use and
expect posix paths.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/