1
edit
Changes
Using filename containing slashes
how you test the distcc-vc? can you debug the exe file? what's the process? ^_^
== Specifying language to cl.exe ==
The Jan 4, 2007 news says:
<blockquote>
Both C/C++ preprocessed file ends in .i. cl has no way of knowning if it's a C/C++ preprocessed file.
</blockquote>
You can solve this problem by specifying the source file type to Visual C++ with /TP (for C++) or /TC (for C). You can also use /tp or /tc for specifying the language for each individual file. Documentation is in MSDN[http://msdn2.microsoft.com/en-us/library/032xwy55(VS.80).aspx].
== Using filename containing slashes ==
The Jan 4, 2007 news mentions that
<blockquote>
cl /cygdrive/c/home/temp/hello.c
</blockquote>
doesn't work, because the path is interpreted as an option. You can solve that by passing the filename (with path) to cl.exe in quotes. If your shell interprets quotes you may need to escape them. For example, from bash you could use
<pre>
cl \"/cygdrive/c/home/temp/hello.c\"
</pre>
