Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Thu, 25 Apr 2002 10:36:55 -0400
From:	Ashok Vadekar <avadekar AT certicom DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Case insensitivity
Message-ID:	<20020425103655.E11836@volta.certicom.com>
Reply-To:	avadekar AT certicom DOT com
References:	<1019697922 DOT 11719 DOT 171 DOT camel AT saratoga> <4 DOT 3 DOT 1 DOT 2 DOT 20020425102144 DOT 016d9848 AT pop DOT ma DOT ultranet DOT com>
Mime-Version:	1.0
In-Reply-To:	<4.3.1.2.20020425102144.016d9848@pop.ma.ultranet.com>; from lhall@rfk.com on Thu, Apr 25, 2002 at 10:27:39AM -0400

It would seem to me that this should be easily accomplished by wrapping
open()/fopen() with code that does some sort of glyph recoding for uppercase
characters.  Getting the library code to access your wrapper would be a minor
macro issue.

While this may not be the answer you were originally looking for, it should
allow you to leave the original code alone, allowing easier rebuilds from
source changes on the original build platforms.

On Thu, Apr 25, 2002 at 10:27:39AM -0400, Larry Hall (RFK Partners, Inc) wrote:
> At 09:25 PM 4/24/2002, B. Joshua Rosen wrote:
> >I'm in the process of porting my CAE tool (hdlmaker) to Cygwin and I've
> >run into a problem with case sensitivity, or to be precise the lack of
> >case sensitivity in the file system. I have a number of files that are
> >paired as upper and lower case versions, i.e. FD.v and fd.v. In the Unix
> >world this is no problem but in the Cygwin environment the files
> >conflict. I noticed the problem when doing a CVS checkout. I'm aware
> >that NTFS is not case sensitive, does Cygwin provide a layer that
> >provides case sensitivity or do I have to go through the huge effort of
> >converting my library to make it case independent.
> 
> While I agree with both Chris's and Rob's response to this thread, in the 
> interest of keeping misinformation out of the email archive, I'll make the
> following statements:
> 
>    1. NTFS *is* case-sensitive.  Windows forces case-insensitivity on it.
> 
>    2. It is possible to create files with the same name differing only by
>       case under Windows using it's API.  There was a patch floating around
>       for Cygwin years ago that did this.  However, it was never incorporated
>       because native Windows tools couldn't deal with the resulting files and
>       the concept couldn't be extended to incorporate directories (as I 
>       recall - of course I'll defer to the email list archives if it states
>       otherwise! ;-) )
> 
> I think you're really pretty much stuck converting your library.
> 
> Larry Hall                              lhall AT rfk DOT com
> RFK Partners, Inc.                      http://www.rfk.com
> 838 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -