Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <384DAE56.8032DECC@cygnus.com>
Date: Tue, 07 Dec 1999 17:03:18 -0800
From: Eric Christopher <echristo AT cygnus DOT com>
Organization: Cygnus Solutions
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: MAKE_MODE changes
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I have a customer complaining about make under a dos window.  Here's a
brief summary of the problem:

Please crearte makefile.
go to DOS command shell.
In the directory with makefile type:
>ren makefile MAKEFILE
and type
>make
MAKE.EXE: *** No targets. Stop.
but when you do
>ren MAKEFILE makefile
and then
>make
make will find makefile and run correctly

I've also seen a notation in the make sources for this:

Pathnames and Case insensitivity:

        Unlike Unix, Windows 95/NT systems are case insensitive but case
        preserving.  For example if you tell the file system to create a
        file named "Target", it will preserve the case.  Subsequent
        access to the file with other case permutations will succeed 
        (i.e. opening a file named "target" or "TARGET" will open the
file 
"Target").

        For example, the following makefile will create a file named
        Target in the directory subdir which will subsequently be used
        to satisfy the dependency of SUBDIR/DepTarget on SubDir/TARGET.
        Without HAVE_CASE_INSENSITIVE_FS configured, the dependency link
        will not be made:

        subdir/Target:
                touch $@
        SUBDIR/DepTarget: SubDir/TARGET
                cp $^ $@

        Reliance on this behavior also eliminates the ability of GNU
        make to use case in comparison of matching rules.  For example, 
        it is not possible to set up a C++ rule using %.C that is
different
        than a C rule using %.c.  GNU make will consider these to be the
        same rule and will issue a warning.


I'd like to make this behavior the default for MAKE_MODE = win32.  Can
anyone see a problem with this or have any problems with it?  This seems
to be a reasonable and even expected behavior under a dos window.

Comments?

-eric

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com