Re: [Tinycc-devel] Basic patch for passing W9X short DOS paths to TCC.

[lostgallifreyan]

Ivo <address@hidden> wrote:
(14/04/2009 17:36)

>On Tuesday 14 April 2009 17:07, lostgallifreyan wrote:
>> What I have considered is using GetLongFileName() in Kernel32.dll to pass
>> long names as specified in the file system. It's a neat answer but only
>> for W98, no good in W95 (and I think redundant in W2K and WXP). Another
>> thing is to add some other option for assembler code files, such as .asm
>> (or .ASM, same thing) for those requiring preprocessing in Windows, and
>> .s (or .S) to be converted in DOS shortname paths so TCC makes the usual
>> interpretation of .s NOT being preprocessed. But I don't know ASM, it's
>> not my call what decision gets made there, and GCC doesn't recognise the
>> extension ASM anyway. For now, if I were to try assembler code I'd just
>> watch carefully what was put into my .s (or .S) files, and make batch
>> scripts with the right extension case for TCC.
>
>Why don't you just implement gcc's -x command line option instead of this 
>ifdeffery? It's also useful on other platforms and it solves the .s/.S 
>problem, too:
>
>-x c
>-x cpp-output
>-x assembler
>-x assembler-with-cpp
>
>etc...
>

I think TCC has that option. If not I'd have to do a lot more than I did. I was 
solving one singular issue only, I wanted a simple DOS shortname path to 
perform as expected in W9X, and I got it. The idea is to present a working TCC 
for Windows newcomers who haven't yet explored deeply. It's also better that 
something as simple as this does work as expected. It works in GCC, so it ought 
to work in TCC. With this patch it does. I deliberately limited to the simplest 
task, because I don't want to break existing handling for more complex matters. 
It's meant to work with TCC, not to reinvent it.