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
Message-ID: <01f601c3fbb7$3c96f960$9a00a8c0@toyon.corp>
From: "Peter J. Stieber" <developer AT toyon DOT com>
To: <cygwin AT cygwin DOT com>
Subject: check_case:strict Useful
Date: Wed, 25 Feb 2004 07:51:27 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

In a different thread CFG wrote:

CFG> I keep pointing out that there few reasons to use the
CFG> check_case:strict option.  Even the person who wrote
CFG> it (Corinna) agrees.  It slows down cygwin's file handling.
CFG> You should only be using this option if you really need it
CFG> and really know what you are doing.

My company generates code for two platforms; Windows and Linux. 95% of the
developers use a Windows based PC with Visual Studio, but the code they
generate must also compile on a Linux box using GCC, so we have them install
cygwin with DOS (Text) mounts and have them use check_case:strict. The
former allows them to build both the VS and cygwin/GCC versions from the
same source. The latter prevents them from committing changes that would
work in VS, but not on Linux (Improper case in a header file name). We do
not use the result of the cygwin build, but instead, use the cygwin
environment as a check of our Linux build before committing. This is very
valuable to us, but I'll admit, an odd situation.

So...

Thanks for adding the feature Corinna and thanks for all of your endless
work on cygwin Chris.

No bug report and a compliment; refreshing eh?
Pete


--
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/