Difference between revisions of "Distcc with MSVC:CL Options"

From CDOT Wiki
Jump to: navigation, search
(CL Options)
(Why CL Options Are Important)
Line 9: Line 9:
 
# some options require things that are only applicable if the entire local code base is around
 
# some options require things that are only applicable if the entire local code base is around
 
# some options require you to send multiple files back (e.g. sending back .obj and .pdb objects is unsupported).
 
# some options require you to send multiple files back (e.g. sending back .obj and .pdb objects is unsupported).
 +
 +
== Questionable Options ==
 +
 +
MSDN has [http://msdn2.microsoft.com/en-us/library/19z1t1wy.aspx categorical listing of cl options].

Revision as of 13:26, 10 November 2006

CL Options

So you'd like to help with the Distcc With MSVC options.

Why CL Options Are Important

The way distcc works is that you send out source code to other machines (called slaves) for them to compile. This speeds up the compilation time. But how can the slave know how to compile this code that was sent to it? What happens is that distcc also sends the compile line to the slave. But it can't be the full line because:

  1. some options don't make sense for the compiler (e.g. options for the linker or the preprocessor).
  2. some options require things that are only applicable if the entire local code base is around
  3. some options require you to send multiple files back (e.g. sending back .obj and .pdb objects is unsupported).

Questionable Options

MSDN has categorical listing of cl options.