Open main menu

CDOT Wiki β

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

(Questionable Options)
(Tutorial: Stupid CL being stupid and not unix)
 
(8 intermediate revisions by 4 users not shown)
Line 11: Line 11:
  
 
= Tutorial =
 
= Tutorial =
This tutorial is a quick way to check if a cl option is supported in distcc. You will have to follow these steps.
+
This tutorial is a quick way to check if a cl option is supported in distcc. You will have to follow these steps:
# create a simple file. Try to #include some things like stdio.h and other .h files.
+
 
# preprocess the file. Use the /P for this, the file will be called <filename>.i
+
1. Open a cygwin bash shell, or the Visual Studio Command prompt<br />
# move the file to some remote location. You can create a temporary folder for this.
+
2. Create a header file called '''sample.h''':
# compile to object code. Pass the /Fo<filename>.obj /c to compile only to object code. If no object code or you get a warning, please give us an email or post in the discussion.
+
 
 +
<pre>
 +
#include <stdio.h>
 +
#define GUARD 0
 +
</pre>
 +
 
 +
3. Create a C file called '''sample.c''':
 +
 
 +
<pre>
 +
#include "sample.h"
 +
#include <string.h>
 +
 
 +
int main(void) {
 +
  return GUARD;
 +
}
 +
</pre>
 +
 
 +
4. Preprocess the file:
 +
$> cl /P sample.c
 +
 
 +
5. create a temporary folder:
 +
$> mkdir temp
 +
 
 +
6. Move the sample.c to temp:
 +
$> mv sample.i temp/
 +
or
 +
move sample.i temp/
 +
 
 +
7. Rename the file sample.c:
 +
$> mv sample.i sample.c
 +
or
 +
$> rename sample.i sample.c
 +
 
 +
8. Compile to '''object code''' and add a command line option listed below. For example:
 +
$> cl /Fosample.obj /c sample.c ''/nologo''
 +
 
 +
9. If you get '''no object code''', '''an error''', or more than ''sample.obj'' being created, please document on this page, or if you feel really unsure, post in the discussion. When documenting please specify if your documentation comes from reading or doing. If reading is not from MSDN please link to where you got your information.  
  
 
== Questionable Options ==
 
== Questionable Options ==
Line 53: Line 89:
 
*/analyze
 
*/analyze
 
*: runs an analysis on the code and will bring up more warnings... This is ok, all it does is increase number of warning messages and may cause build to fail but the user did '''ask''' for it, so that's fine. (from reading).
 
*: runs an analysis on the code and will bring up more warnings... This is ok, all it does is increase number of warning messages and may cause build to fail but the user did '''ask''' for it, so that's fine. (from reading).
 +
*/c
 +
*: only compile, don't link. (from doing)
 
*/doc
 
*/doc
 +
*: generate sone documentation in a xdc file. Killing this option since you can't get the file back from the slave.
 
*/errorReport
 
*/errorReport
 
*/FC
 
*/FC

Latest revision as of 22:46, 19 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).

Tutorial

This tutorial is a quick way to check if a cl option is supported in distcc. You will have to follow these steps:

1. Open a cygwin bash shell, or the Visual Studio Command prompt
2. Create a header file called sample.h:

#include <stdio.h>
#define GUARD 0

3. Create a C file called sample.c:

#include "sample.h"
#include <string.h>

int main(void) {
  return GUARD;
}

4. Preprocess the file:

$> cl /P sample.c

5. create a temporary folder:

$> mkdir temp

6. Move the sample.c to temp:

$> mv sample.i temp/
or
move sample.i temp/

7. Rename the file sample.c:

$> mv sample.i sample.c
or
$> rename sample.i sample.c

8. Compile to object code and add a command line option listed below. For example:

$> cl /Fosample.obj /c sample.c /nologo

9. If you get no object code, an error, or more than sample.obj being created, please document on this page, or if you feel really unsure, post in the discussion. When documenting please specify if your documentation comes from reading or doing. If reading is not from MSDN please link to where you got your information.

Questionable Options

MSDN has categorical listing of cl options.

  • /arch
  • /bigobj
  • /clr
  • /EH
  • /favor
  • /fp
  • /G1
  • /G2
  • /Gd
  • /Ge
  • /GF
  • /Gh
  • /GH
  • /GL
  • /Gm
  • /GR
  • /Gr
  • /Gs
  • /GT
  • /GX
  • /Gy
  • /Gz
  • /MD
  • /MDd
  • /MT
  • /MTd
  • @
    lets you add a file with compiler options. This must be eliminated as the file can't be sent to the slave. (for reading)
  • /?
    You'd think this would cause problems but distcc leaves it be... OK! (from reading)
  • /analyze
    runs an analysis on the code and will bring up more warnings... This is ok, all it does is increase number of warning messages and may cause build to fail but the user did ask for it, so that's fine. (from reading).
  • /c
    only compile, don't link. (from doing)
  • /doc
    generate sone documentation in a xdc file. Killing this option since you can't get the file back from the slave.
  • /errorReport
  • /FC
  • /H
  • /HELP
    You'd think this would cause problems but distcc leaves it be... OK!
  • /hotpatch
  • /J
  • /nologo
  • /QIfist
  • /QIPF_B
  • /QIPF_C
  • /QIPF_fr32
  • /QIPF_noPIC
  • /QIPF_restrict_plabels
  • /showIncludes
  • /Tc/TC
  • /Tp/TP
  • /V
  • /W
  • /w
  • /Wall
  • /WL
  • /Zm