[Bf-committers] MinGW debug builds do not run

Peter Kümmel syntheticpp at gmx.net
Wed Feb 23 20:01:25 CET 2011

On 23.02.2011 10:45, Nathan Letwory wrote:
> Hash: SHA1
> On 21.2.2011 1:15, Peter Kümmel wrote:
>> It compiles now out of the box but still crashes.
>> Seems I have to go the 'hard' way you described.
> Python 3.1 debug dll is built dynamically linking against msvc9 debug
> runtime, so if you want to run debug with other than vs2008, you'll have
> to acquire the appropriate debug runtime dlls. These are not
> redistributable, so you'll need to get vs2008 (I assume the express
> version will do, but can't tell for sure).
> You could also rebuild python 3.1 debug dll with mingw, if that's
> possible, I suppose. And when using vs2010, you could rebuild the python
> 3.1 debug dll with that.

OK. Is it possible that these dlls get added to subversion?
I would update the cmake rules then.


> Anyway, have the correct debug runtime dlls in the same dir as
> blender.exe, and you should be running fine.
> /Nathan
>> On 20.02.2011 14:46, Campbell Barton wrote:
>>> IIRC MSVC2008 full version is used for releases,
>>> I have a free MSVC2010 which has a similar problem to MinGW, debug
>>> builds fail to run with strange popup dialog error.
>>> Re Crash on startup:
>>>    If its a crash (not a linking/error message), best not assume blender
>>> is without fault, debug info&   call-stack can help a lot in tracking
>>> down these problems.
>>> The IOError define is already in lib/windows, committed shortly after
>>> changing the exception.
>>> I use an update alias which does both repo's before building to
>>> prevent these kinds of errors.
>>> Do you still get the crash on startup?
>>> On Sun, Feb 20, 2011 at 11:54 AM, Peter Kümmel<syntheticpp at gmx.net>   wrote:
>>>> On 20.02.2011 04:24, Campbell Barton wrote:
>>>>> Whats supported isn't set in stone, its more a case of which
>>>>> configurations are tested&     known to work.
>>>> OK, thanks. And what is mostly used for the Windows releases?
>>>>> this works for me.
>>>>> - windows xp
>>>>> - mingw-gcc4.5.2, (from mingw's main site)
>>>>> - cmake 2.8 (build type set to Release or RelWithDebInfo)
>>>>> - blender (tested r34959)
>>>> I had a little bit outdated checkout with 4.4, W7-64Bit, and
>>>> problems with release and debug.
>>>>> A crash on startup may be a real bug rather then lack of support, you
>>>>> could run with gdb and see why its crashing.
>>>>> If you are unable to figure out how to fix you could file a bug and
>>>>> include a backtace.
>>>> I assume not really a error in blender code, it's the mixture of
>>>> pre-compiled binaries, compiler used for blender, OS, and runtime
>>>> libraries.
>>>> Best is to build everyting with the same compiler.
>>>>> Another way to help find the cause of the crash is to disable all
>>>>> WITH_* options in cmake configuration, WITH_OPENAL, WITH_IMAGE_OPENEXR
>>>>> ... etc.
>>>>> If this works you could try again with usable settings (so you get an
>>>>> interface),
>>>> I already had the idea to try it without python ;)
>>>>> After that its trial and error to see which library causes the crash,
>>>>> the offending lib could be disabled by default with mingw until its
>>>>> fixed properly.
>>>>> One other thing, you were getting the error 'PyModule_Create2'
>>>>> interestingly I got this error too on Linux when trying to load a
>>>>> library built with a debug python but finding a release library.
>>>> I could link against the lib/windows version with attached patch.
>>>>> On Sat, Feb 19, 2011 at 3:26 PM, Peter Kümmel<syntheticpp at gmx.net>     wrote:
>>>>>> Tested it with cmake too. It links after a small fix, but
>>>>>> crashes immediately after starting. Seems mingw isn't supported.
>>>>>> Peter
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> ZZSzd9oe9PYgyZqJ3AylmdozyNaEg//EuLFtWQnFqov9XE/tuK/8ZNVOD3Ro2hLK
> tZ6Z38eQjkXaMOrXR/R+yZnbRutsru3P6xqTHfZY7Au65Z8BQaW1LxXZD0LRrB+p
> ITMxB3Tn17wxDEj7AJywVKB4GHhFUMo0vaVdB5LLjnpMXpB+wjGSrvhyZQUStGnb
> y05TAxR+Z6fXgvtHrf967PQAeoVVjdigyCY0UNtOg4YMDAeHSVeIQqYHSsPvXmru
> B4383jq4q/mnUgOcgYJhSrFr1mSx0f7LmeMdWcq6G2XHK+8NTS7aZ8x9pY0xMdE=
> =ifdD
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list