when trying to port the lwIP Demo to gcc (that i use under linux), i noticed that several header files were included with a different filename letter case as in the actually existing filename.
most of these files are inside that demo dir/subdirs, but there's at least 2 of them also in the main FreeRTOS source trunk.

this isn't a problem for people developing under windows, since windows is case insensitive. for those using a case-sensitive os like linux, it is impossible to #include "foo.h" when the actual file is called "Foo.h".

the concerned files (only those i found when trying to compile this demo) can be seen here:
ln -sf usb.h USB/USB.h
ln -sf Board.h board.h
ln -sf Emac.h EMAC/emac.h
ln -sf SAM7_EMAC.h EMAC/sam7_emac.h
ln -sf cpu.h lwip-1.1.0/contrib/port/FreeRTOS/AT91SAM7X/arch/CPU.h
ln -sf ioat91sam7x256.h ../../Source/portable/GCC/ARM7_AT91SAM7S/ioAT91SAM7X256.h
ln -sf AT91SAM7X256.h ../../Source/portable/GCC/ARM7_AT91SAM7S/at91sam7x256.h

the syntax in all these cases is that of a symlink: ln -sf really_existing_filename_without_path relative_path_to_really_existing_file/filename_as_included_in_c_files )

could you please fix that so the letter case in the #include is the same as in the actual filename ?

thanks and regards,
frank

Thanks for the info. I can only test under Win32, so need other people to point these out.

here's another one:
in the gcc-based demos i've had a look at, the Makefile
is called 'Makefile' but appears as a dependency to several targets under the name 'makefile'.

my local quick-fix was again to place a soft-link makefile -> Makefile, but it would be cool if it could be called 'Makefile' everywhere (as the file is actually named. this is the default letter case)