You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by David Bertoni <db...@apache.org> on 2008/03/26 21:20:33 UTC

Windows file manager for Cygwin

Hi all,

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.

Also, it looks like with the Posix manager on Cygwin, you cannot specify 
Windows-style paths like you could with the old file manager.  This is 
because PosixFileMgr::isRelative() simply looks at the first character to 
see if it's "/".

Perhaps we need a specialized Cygwin file manager?  Any thoughts?

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


Re: Windows file manager for Cygwin

Posted by Gareth Reakes <ga...@we7.com>.

David Bertoni wrote:
> Boris Kolpackov wrote:
>> Hi David,
>>
>> David Bertoni <db...@apache.org> 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.


Any users out there with opinion?

Gareth


-- 
Gareth Reakes, CTO                                 WE7
+44-20-7117-0809                    http://www.we7.com

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


Re: Windows file manager for Cygwin

Posted by James Berry <jb...@apache.org>.
On Mar 27, 2008, at 9:38 AM, David Bertoni wrote:

> James Berry wrote:
>> 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?
> I think so, but my impression is we've been trying to reduce the  
> amount of conditional compilation with these changes.
>
> Let me work up a quick patch and I'll post the results.  It should  
> be fairly straightforward.

Somewhere there's a tradeoff between a bit of conditional compilation  
and the sort of mad proliferation of almost-the-same files we had in  
xerces2.

James

Re: Windows file manager for Cygwin

Posted by David Bertoni <db...@apache.org>.
James Berry wrote:
> 
> On Mar 26, 2008, at 3:49 PM, David Bertoni wrote:
> 
>> Boris Kolpackov wrote:
>>> Hi David,
>>> David Bertoni <db...@apache.org> 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?
I think so, but my impression is we've been trying to reduce the amount of 
conditional compilation with these changes.

Let me work up a quick patch and I'll post the results.  It should be 
fairly straightforward.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


Re: Windows file manager for Cygwin

Posted by James Berry <ja...@jberry.us>.
On Mar 26, 2008, at 3:49 PM, David Bertoni wrote:

> Boris Kolpackov wrote:
>> Hi David,
>> David Bertoni <db...@apache.org> 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

Re: Windows file manager for Cygwin

Posted by David Bertoni <db...@apache.org>.
Boris Kolpackov wrote:
> Hi David,
> 
> David Bertoni <db...@apache.org> 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.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


Re: Windows file manager for Cygwin

Posted by Boris Kolpackov <bo...@codesynthesis.com>.
Hi David,

David Bertoni <db...@apache.org> 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.

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.

Boris

-- 
Boris Kolpackov, Code Synthesis Tools
Open source XML data binding for C++:   http://codesynthesis.com/products/xsd
Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org