How does Cons deal with case insensitivity in Windows NT?
I have a problem in NT because of the odd case-insensitivity of NT. If I have one .c file that ‘#includes “abc.h”‘ and another that ‘#include “ABC.H”‘, they are really including the same file (assuming the same directory or include path, etc.). NT remembers the case that was used to create the file so the filename might be “abc.H”, or “Abc.h”, whatever, but the name is case insensitive because no matter what case you use to open the file, it will work. But cons treats them as different. The real problem is where “abc.h” is generated or “Installed” into the location where the compiler will find it. The file is not created in time and/or it is deleted (i.e. unlinked from the Link directory). When scanning .c files for #includes, if I change all the include file names to lower case, then things behave as expected.
