grischka <gris...@gmx.de> wrote: (07/04/2009 18:18) >> I'm not after complexity, just looking for the neatest way to >> be sure that a newcomer can fire up TCC within about three >> attempts at various optuions Windows offers. It;s when it >> won't work after five or more that people run out of ideas >> and start asking stuff. > >Okay, so lets test a simple step by step tutorial: > >1) Download >http://download.savannah.nongnu.org/releases/tinycc/tcc-0.9.24-win32-bin.zip >2) Unzip to a directory on your computer to your choice >3) Add that directory to your system PATH variable >4) Open a console window (DOS box) and "cd" to the examples subdirectory >5) type> tcc hello_win.c >6) type> hello_win > >Does this work for you? >
Yes, and it's a good decription of procedure worth adding to main help. It would also be nice for the other major method to work though, and I discovered that one simple change will do it. C:\WINDOWS\Desktop>F:\TCC\TCC.EXE F:\TCC\EXAMPLES\HELLO_~2.C F:/TCC/EXAMPLES/HELLO_~2.C:1: unrecognized file type C:\WINDOWS\Desktop>F:\TCC\TCC.EXE F:\TCC\EXAMPLES\HELLO_~2.c These show that TCC is only accepting the lower case C in the manually edited drag/dropped auto-written shortname path. If TCC were edited to allow both cases for that .c extension, all would be well. It's not that it needs to understand these paths at all, it just has to not block them because the second instance worked fine, so clearly that business with the tilde and the numbers doesn't bother TCC at all. Just needs C as well as c to be accepted. _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tinycc-devel
