David Haney - 2007-05-13

Logged In: YES
Originator: YES

I recall running into an issue with HP where I was unable to use aCC in order to compile some C files, but the native cc compiler worked okay. In that case I would expect .C files to go to the aCC compiler instance, and .c files to go to the cc compiler. As long as the comparison is case-insensitive, it seems like the files would go to one or the other regardless of the bid priority (If I double the bid for .c in one of the compilers, that double-bid will apply to .C files as well).

Instead of making the decision in the AbstractProcessor, what about making that method abstract, and requiring the downstream compiler/linker implementions define whether they perform their bids in a case-sensitive or insensitive manner. For example, all of the Unix compilers could provide implementations that assume case-sensitive, and be explicit which cases they support, while the Windows compilers could provide implementations that assume case-insensitive. The only one that seems hairy would be gcc, which may require different behavior depending on the OS, but that could be resolved for that compiler by checking the platform that we're on.

I don't have a test case for this scenario at the moment, so I can't verify if this is still an issue, or if there was just a problem with the library I was attempting to compile at the time. This probably isn't a high-priority issue.