take a look at gecc (http://gecc.sf.net) it is designed to handle a changing set of compilation nodes. It is work in progress, but maybe you would take a look at it. It does not required the same header file nor all the libs installed on alle the compilation nodes, only the compiler (gcc).
you could combine the distribution with object file caching. gecc (http://gecc.sf.net ) shows this. It is work in progress but you could take a look at it if you are interessted.
There is an alternative ( http://gecc.sf.net). gecc has a little different approach, it has a central component that distributes the compilation to a number of compile nodes. The set of compile nodes may change (over time). That is: compile nodes may come and go.
gess is work in progress, distcc is much more mature, but maybe you like to take a look at gecc also.
gecc (http://gecc.sf.net) takes care of that and finds a compile node that uses the same compiler. Think of something like mozilla, that uses C and C++. gcc and c++ could invoke different compiler (at leat different versions).
Slashdot Mirror
take a look at gecc (http://gecc.sf.net) it is designed to handle a changing set of compilation nodes. It is work in progress, but maybe you would take a look at it. It does not required the same header file nor all the libs installed on alle the compilation nodes, only the compiler (gcc).
you could combine the distribution with object file caching. gecc (http://gecc.sf.net ) shows this. It is work in progress but you could take a look at it if you are interessted.
it really depends on your dependencies. Something
like mozilla scale really well, with distcc and with gecc (http://gecc.sf.net/ ).
For smaller project (like 100k source) the gain is smaller.
have you tried to compile KDE with distcc or gecc (http://gecc.sf.net ) ?
but than you need all the header and lib files on
all the compilation node. neither distcc nor gecc (http://gecc.sf.net ) need this.
There is an alternative ( http://gecc.sf.net). gecc has a little different approach, it has a central component that distributes the compilation to a number of compile nodes. The set of compile nodes may change (over time). That is: compile nodes may come and go.
gess is work in progress, distcc is much more mature, but maybe you like to take a look at gecc also.
(yes, gecc is my baby)
gecc (http://gecc.sf.net) takes care of that and
finds a compile node that uses the same compiler. Think of something like mozilla, that uses C and C++. gcc and c++ could invoke different compiler (at leat different versions).