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
X-pair-Authenticated:	24.126.73.164
Message-ID:	<3D80B0F2.4FA96119@kegel.com>
Date:	Thu, 12 Sep 2002 08:21:22 -0700
From:	Dan Kegel <dank AT kegel DOT com>
X-Accept-Language:	en
MIME-Version:	1.0
To:	Bruce Adams <bruadams AT tycoint DOT com>
CC:	cygwin AT cygwin DOT com, crossgcc AT sources DOT redhat DOT com
Subject:	Re: Preprocessing Assembly
References:	<C9150052B112D3119E9E0004ACA6E437025AFCA8 AT tepg1 DOT tepg DOT co DOT uk>

Bruce Adams wrote:
>     I am using gcc to cross compile for m68k.  I discovered the following on
> the net.
> 
> "Both .S and .s are assembler. By convention, .S is assembly source that
> needs to be preprocessed. Otherwise, gcc doesn't care."
> 
> This is of course less than optimal on windows as the filesystem is not case
> sensitive.

NTFS preserves case.  I think the .s / .S trick should work fine as long
as your editor and other tools don't itself muck up the filename.
- Dan

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