 |
 |
 |
 |
 |
 |
 |
- What programming languages does DistriBuild support?
- Currently DistriBuild support only C++ builds.
- Do i need to install Visual Studio or any components of it (compiler, linker, etc.) on machines that are only serving their CPU power for DistriBuild?
- No, you have to install only the "Worker machine" package on such machines if you wish to utilise their CPU power. No part of the development environment is needed. DistriBuild automatically transfers all needed executables, libraries and other files to the worker machine. Nothing is installed, all these files are kept in private directory and cached there. Also the source code being subject to compilation is cached.
- What about usage of storage space for caching?
- DistriBuild tries to minimize usage of storage space. For example, when one server machine caches the same source file for many client machines, the file is really stored only once. This is typical situation in programming teams, where entire team is working on one project and therefore share most files. On the other hand, when there are multiple versions of the same file, they are stored separately. Identity of files is detected by MD5 checksums. The cache also allows to set overall occupation limit, when it's reached the least recently used files are automatically removed, to keep the allocated space within the limit.
- Is it similar in technology to distcc?
- No, DistriBuild uses a different approach. It can do all stages of the compilation on the remote machine, as opposed to distcc which does all C++ preprocessing phase on the client machine (thus reducing parallelism).