On Mar 26, 2008, at 3:49 PM, David Bertoni wrote:

Boris Kolpackov wrote:
Hi David,
David Bertoni <[EMAIL PROTECTED]> writes:
I was just building the 3.0 beta on Cygwin, and noticed that configure chooses the Windows file manager instead of the Posix one. I think this
is wrong, because it means you cannot use Cygwin/Unix-style paths.
Agree. We should prefer the Posix manager by default.
Also, it looks like with the Posix manager on Cygwin, you cannot specify
Windows-style paths like you could with the old file manager.
I think this is fine. Cygwin's goal is to present Windows as UNIX- like with UNIX-style filesystem. I then don't see why software that is built
for Cygwin should worry about Windows-style paths. AFAIK, most of the
software for Cygwin only supports UNIX-style paths.
Actually, most of the Cygwin utilities I've used support both styles, including the form "c:/foo/bar.txt." In fact, there is the cygpath utility that converts from one to another.

In case of Xerces-C++, anybody wanting Windows-style path support
should instead use either MSVC or Mingw.
Perhaps we need a specialized Cygwin file manager?
No, I don't think we should have one.
Then we'ed better document this change in behavior from the 2.x releases.

Is there an easy patch to the POSIX file manager that could be conditionally compiled in to add the additional relative path support in the case of a Cygwin environment?

James

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to