<div>After the release happened, Chris added Python 2.5 building for CMake to the SVN: <a href="http://lists.blender.org/pipermail/bf-blender-cvs/2007-May/009960.html">http://lists.blender.org/pipermail/bf-blender-cvs/2007-May/009960.html
</a>.</div>
<div> </div>
<div>There are still a few odd CMake issues (the debug one Steve mentions and some ffmpeg dlls trying to be added to the release folder when they don't exist:</div>
<div> </div>
<div>in IF(WITH_FFMPEG)<br> COMMAND copy /Y \"${WIN_LIBDIR}\\ffmpeg\\lib\\libdts.dll\" \"$\(TargetDir\)\\\"<br> though<br> COMMAND copy /Y \"${WIN_LIBDIR}\\ffmpeg\\lib\\xvidcore.dll\" \"$\(TargetDir\)\\\")
</div>
<div> </div>
<div>But Cmake can still get a good build out with Python 2.5 :)</div>
<div> </div>
<div> </div>
<div>sfogoros wrote:<br>> Oh, I guess I should have said this is from the 2.44 release tree. It's<br>> not configured for python25 as far as I know.<br>><br>> Steve<br><br>True :) The Windows release binaries are built with SCons, I don't know
<br>how much cmake is in use on Windows. At least it hasn't been kept<br>up-to-date with the current progress. I just meant to say that, while<br>you are at making changes to your own system, make sure you build<br>against
2.5, since that's what the official release does as well.<br><br>/Nathan</div>