Yamyam: 1版をインポートしました

2018-06-28T21:14:50Z

1版をインポートしました

wiki>Ideasman42: /* Build System */

2017-07-21T10:02:59Z

‎Build System

新規ページ

= distcc =

distcc is a tool to distribute building C/C++ software across multiple Unix like systems.

This project has its own documentation, so this is just some notes on using it with Blender.

* For reference, the web-page for distcc can be found here:<br>https://github.com/distcc/distcc
* For community maintained docs, See the arch wiki:<br>https://wiki.archlinux.org/index.php/Distcc

== Use Case ==

For incremental rebuilds and general development, there aren't significant advantages to distributing the process.

This is mainly useful when you need to rebuild the entire source tree, many times.

* Using <tt>'''git bisect'''</tt>.
* Changing compiler flags.
* Changes to heavily used headers.

== Configuration ==

* Install <tt>distcc</tt> using your systems package manager on 2 or more systems.

In the following example, <tt>192.168.1.100</tt> is the master, and <tt>192.168.1.200</tt>, <tt>192.168.1.201</tt> are the slaves.

=== Master ===

Edit <tt>'''/etc/distcc/hosts'''</tt>

Example configuration:

192.168.1.200/16,lzo,cpp 192.168.1.201/16,lzo,cpp localhost/8,cpp

Note that the values 16 and 8 represent the number of jobs you want each system to be given.

* <tt>'''cpp'''</tt> means the pre-processing is done on build the slaves too.
* <tt>'''lzo'''</tt> uses lzo compression for file transfer.

=== Slaves ===

Edit <tt>'''/etc/default/distcc'''</tt>

Example configuration:

STARTDISTCC=true
ALLOWEDNETS="192.168.1.100"

== Build System ==

First start the distcc service on master and slave systems.

<source lang="bash">
systemctl start distccd
</source>
''... replace 'start' with 'enable' if you want this to be stated each reboot.''

In this example we'll assume your source directory is called <tt>'''blender/'''</tt> and create a new build directory called <tt>'''build_distcc/'''</tt>.

The following commands assume you're in an existing Blender checkout.

''(Authors note, in CMake 3.4x you should not need to change the compiler, instead use [https://stackoverflow.com/a/34317588/432509 CMAKE_<LANG>_COMPILER_LAUNCHER]. This needs to be tested though before updating the docs! [[User:Ideasman42|Ideasman42]] 10:02, 21 July 2017 (UTC))''

<source lang="bash">
mkdir ../build_distcc
cd ../build_distcc
CC="distcc gcc" CXX="distcc g++" cmake ../blender
</source>

This should configure the new build without any errors.

Now compile the source.

<source lang="bash">
pump make -j32
</source>

In this example the number of jobs is 32, jobs will be split across all systems.
To keep all cores busy you can set the job count to slightly more than the sum of all cores - since there will be network latency where cores wait for new jobs.

== Notes ==

* Building with the instructions above you may get the warning <tt>'''-Wmissing-include-dirs'''</tt> which can be safely ignored.
* When the <tt>'''distcc'''</tt> daemon isn't running, it will print a warning and fall-back to building locally.
* If you try to modify an existing build to use <tt>'''distcc'''</tt>, CMake will detect the compiler as being changed and remove your existing <tt>'''CMakeCache.txt'''</tt> and create a new one (loosing any manual edits!).

← 古い版	2018年6月28日 (木) 21:14時点における版
(相違点なし)

Dev:Doc/Tools/distcc - 版の履歴

Yamyam: 1版 をインポートしました

wiki>Ideasman42: /* Build System */

Yamyam: 1版をインポートしました