How to download the code¶
BURP is built from many different modules, some of which have different opensource licenses. On this page you can get an overview of what modules we have and how to get access to the code. A great thanks goes out to the Contributors who have already helped with the development of BURP. If you wish to help out too you can check out some of the opensourced subprojects above.
All development is managed here in the development manager as well as in the 'development'-part of the forum.
For read-only access you can use the user "anonymous".
The main component of BURP is the server back-end and front-end.
SVN link: http://development.renderfarming.net/svn/repos/burp/server/trunk (Web SVN Browser)
CATS is the Compact Automated Transfer System used for transferring raw results to users in an easy way as soon as the frames are finished. CATS is developed in Java to be as cross-platform and easy to use as possible.
SVN link: http://development.renderfarming.net/svn/repos/burp/cats/trunk (Web SVN Browser)
Glue Client-side Code¶
The client-side code is compiled into the client applications that are sent out to participants of the BURP project. The code is heavily similar to the wrapper application from BOINC and it is potentially capable of running any renderer with the correctly formatted output. It basically acts as the glue that binds BURP, BOINC and any compatible renderer together.
SVN link: http://development.renderfarming.net/svn/repos/burp/server/trunk/clients/glue3 (Web SVN Browser)
How to compile: Compiling Glue
BURP Blender renderer patches¶
This set of patches enables the Blender internal renderer to work with the BURP Glue.
General requirements for a BURP patch for renderers can be found in this forum post.
SVN link: http://development.renderfarming.net/svn/repos/burp/server/trunk/clients/blender (Web SVN Browser)