<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Sergey,<br>
thanks a lot for working on this, I appreciate it! <br>
<br>
Will check it out now. <br>
<br>
Best regards,<br>
Thomas<br>
<br>
Am 15.11.2014 um 16:54 schrieb Sergey Sharybin:<br>
</div>
<blockquote
cite="mid:CAErtv24pqTEnwLggaVY91HPyZ1zLWQ=WANQpjiV7aPb8r68ihg@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>Last few evenings i've been working on making a dedicated
repository for Cycles renderer and at this point it seems to
be ready for public access now, even though some more work is
required.</div>
<div><br>
</div>
<div>= Motivation =</div>
<div><br>
</div>
<div>Main motivation of creating standalone repository for
Cycles is to simplify access for new developers who wants to
hack into Cycles code but don't want to bother cloning the
whole Blender repository and setting up environment for
blender compilation.</div>
<div><br>
</div>
<div>It was kind of possible to only compile Cycles from Blender
repository as well, but that process was really tedious.</div>
<div><br>
</div>
<div>= What repository contains =</div>
<div><br>
</div>
<div>Repository contains the full history of Cycles, starting
from the original commit to the Blender SVN. This means it's
possible to track down every change in the sources. The only
thing here is that it's not possible to compile old sources.
This is because build system for standalone repository was
added just now and trying to put it somewhere in the past was
rather tricky.</div>
<div><br>
</div>
<div>Sources are mainly a direct dump from Blender, so it
shouldn't be difficult to keep Cycles in Blender and
standalone repositories in sync. There are a bit of changes to
build system which we'll need to backport to blender (namely
CMake variables name convention).</div>
<div><br>
</div>
<div>Repository contains README file which describes how to
compile Cycles. Compilation is so called "works for me", so
more tweaks are likely needed before compilation becomes
flawless for everyone.</div>
<div><br>
</div>
<div>*NOTE*: Windows is not supported atm! It's because of some
dependencies which are not so clear to get. Mainly OpenGL,
GLUT and GLEW. Don't worry, we will support Windows
eventually, we just need to start from something!</div>
<div><br>
</div>
<div>The repository also contains folder with .xml examples, so
it's really easy to test render engine just after compilation.</div>
<div><br>
</div>
<div>= Build system =</div>
<div><br>
</div>
<div>Currently CMake is used as a build system, and likely it'll
be it,</div>
<div><br>
</div>
<div>= Where the repository is =</div>
<div><br>
</div>
<div>It is on our server, read-only access is</div>
<div><br>
</div>
<div> git clone <a class="moz-txt-link-freetext" href="git://">git://</a><a moz-do-not-send="true"
href="http://git.blender.org/cycles.git">git.blender.org/cycles.git</a><br>
</div>
<div><br>
</div>
<div>for write access (needs SSH key and you need to be a
developer of the project)</div>
<div><br>
</div>
<div> git clone <a class="moz-txt-link-abbreviated" href="mailto:git@git.blender.org:cycles.git">git@git.blender.org:cycles.git</a><br>
</div>
<div><br>
</div>
<div>To browse repository online please visit:</div>
<div><br>
</div>
<div> <a moz-do-not-send="true"
href="https://developer.blender.org/diffusion/C/">https://developer.blender.org/diffusion/C/</a></div>
<div><br>
</div>
<div>= Authors =</div>
<div><br>
</div>
<div>The repository contains the file with everyone who
contributed to Cycles. This is somewhat common for all open
source projects to have such a file.</div>
<div><br>
</div>
<div>Currently this file contains authors of commits, so if
someone submitted patch which was committed by someone else
please let me know -- that'd be easier than reading all the
commit messages searching for such information.</div>
<div><br>
</div>
<div>= Synchronization with Blender =</div>
<div><br>
</div>
<div>Ideally we'll need to have some automated way to sync
changes between Blender and Cycles, but it is not done yet.
Exact way how to keep things in sync i'll publish later.</div>
<div><br>
</div>
<div>For now we can do manual synchronization, which is not THAT
bad.</div>
<div><br>
</div>
<div>= Known TODOs =</div>
<div><br>
</div>
<div>
<div>- Windows build is not supported at this moment.</div>
<div>- Logging option is exposed as an option but wouldn't
work now.</div>
<div>- Installation target is not tested and would need more
work.</div>
<div>- Compiled .oso files are not put to the final location,
so manual copy is required for now.</div>
</div>
<div>
<div>- Set up mailing list for commits (if we need one?)</div>
<div><br>
</div>
<div>I'm pretty much sure i forgot to put some information in
this email which i wanted, but the mail becomes too long
already, so i'd rather wrap up now and answer the questions
as they arrive.</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div><span style="color:rgb(102,102,102)">With best regards,
Sergey Sharybin</span></div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bf-cycles mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a>
<a class="moz-txt-link-freetext" href="http://lists.blender.org/mailman/listinfo/bf-cycles">http://lists.blender.org/mailman/listinfo/bf-cycles</a>
</pre>
</blockquote>
<br>
</body>
</html>