[Bf-committers] python32_d.dll requires MSVC9
If VC9 is not installed, Blender debug builds quit with an application was unable to start correctly error as soon as they try to load the Python library. The problem is that python32_d.dll was built with the VC9 debug CRT dynamically linked, and that the debug CRT is available only through an install of VC9. The solution is simply to recompile the DLL with the runtime statically linked (/MTd). This is the only thing preventing VC10 builds from succeeding! ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] python32_d.dll requires MSVC9
Steady on, nobody is suggesting that. ;-) On 21/07/2011 4:28, Shaul Kedem wrote: Well, not only... when running cmake with VC10 in builds that require boost and ioimage libs it will fail on them as well. If we want to upgrade to VC10 I think that we should abandon VC9 and do the move once and for all On Thu, Jul 21, 2011 at 8:12 AM, Tom Edwardscont...@steamreview.org wrote: If VC9 is not installed, Blender debug builds quit with an application was unable to start correctly error as soon as they try to load the Python library. The problem is that python32_d.dll was built with the VC9 debug CRT dynamically linked, and that the debug CRT is available only through an install of VC9. The solution is simply to recompile the DLL with the runtime statically linked (/MTd). This is the only thing preventing VC10 builds from succeeding! ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] python32_d.dll requires MSVC9
To be able to compile Blender using MSVC 2010 (x86 at least) without recompilling some of the libraries you need to disable: - Openexr - Opencollada And this is for non debug builds. This way Blender builds and is quite stable when compilled with MSVC 2010. Is possible to compile Blender using MSVC 2010 with all the features enabled, but this require you manually recompille using MSVC 2010: - Python - Openexr - OpenCollada - Zlib (for x86 only, x64 will build fine) And manually replace these on the LIB directory, or modify the cmake scripts and filelists for the linking phase. Scons will build only if you replace the old libraries in the LIB folder for the new libraries, since scons is still not updated to support MSVC 2010 (x86) and/or MSVC 2010+Windows 7 x64 SDK (for x64 builds), and will use the components taken from the environment assuming that MSVC 2008 is installed. And if you want to build cycles, you really need to recompile all it's dependencies. Good Luck with Boost ;). I've uploading builds done with MSVC 2010 to graphicall in the past, but Real Life (TM) issues keeps me to do anything serious nowadays. Maybe in the future i will upload again these, but don't hold your breath for now. Regards. J. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] python32_d.dll requires MSVC9
Sorry, is not really needed to recompile Python in the release builds, but only on debug builds. Regards J. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
