RE: [avr-chat] Re: WinAvr 2005... compile problems

[Dave Hylands]

Hi J"org,

> To the contrary, I have yet to see a single project created on Unixen
> that would fail to also compile on Windows because of filename
> problems.

I'll give you a couple that bug me:

1 - glibc (cross compiling under Windows for an embedded linux system)
I can't remember the exact problem, but it was something like having *.os
files and *.OS files

2 - the linux kernel, in particular the netfilter stuff (also cross-compiling
for an embedded linux system).
It has files like: ipt_tcpmss.c and ipt_TCPMSS.c which are different.

Personally, I prefer to keep my stuff as if it were case sensitive even if it
doesn't matter. That way my stuff works on case-sensitive as well as
case-insensitive scenarios.

> Partially, the problem has been around all the time: the compiler
> driver (avr-gcc[.exe]) always makes case-sensitive decisions about
> potential filename suffixes.  Of course, it doesn't matter to the
> compiler driver that foo.C would reach the same file as foo.c in the
> filesystem, yet it would treat the first one as C++ if you spell it
> that way on the command-line (and thus, if you spell it that way in
> your Makefile).  Likewise, foo.S (spelled that way on the compiler
> command-line) will always make the compiler treat it as assembler
> source to be preprocessed.

Yep - I know lots of people that have been caught by the *.s versus *.S
issue.

--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/