It compiles now out of the box but still crashes. Seems I have to go the 'hard' way you described.
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<[email protected]> 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), >>> all off except WITH_PYTHON WITH_INSTALL and WITH_PYTHON_INSTALL. >> >> 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<[email protected]> wrote: >>>> >>>> Tested it with cmake too. It links after a small fix, but >>>> crashes immediately after starting. Seems mingw isn't supported. >>>> >>>> Peter >>>> _______________________________________________ >>>> Bf-committers mailing list >>>> [email protected] >>>> http://lists.blender.org/mailman/listinfo/bf-committers >>>> >>> >>> >>> >> >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> >> > > > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
