Sorry if this has been asked and answered before, but I haven't found it yet. Still looking through past messages, but there's a lot out there.
I've finally got Blender to compile, but when I run the blender.exe from the 'install' directory, it get a large, blank, grey screen and then a popup about "Blender has stopped working". So obviously, I've missed something.
I'm working on a 64-bit, Windows 7 PC.
I'm trying the 32-bit build using SCONS and MinGW. I've got it to compile. I don't think there are any compile errors, but it's a long compile and some of it scrolls by too fast. (Is there an easy way to log compile messages??)
Do I have to go the 64-bit route, since I'm on a 64-bit machine? I can run both 32 & 64 bit downloaded blenders.
I stayed away from the 64-bit build once I started to read about it being 'experimental'.
With out any other error message, I'm not sure what to try.
The usual cause of missing menus and such is running blender from the build directory instead of the install dir.
I'm running from the install directory. If it were something missing, I might come up with a guess of where/what to look at. But it just won't start, even with command line debugging on, there's no output.
That path command is in my compile batch script. Just checking if it made any difference in running Blender or not. No difference. I get the same popup about it stopped working. No output to the DOS window I start it from. No separate system console opens.
Same thing, just that popup, running:
I can run both 64 & 32-bit Blender 2.63a downloads from http://www.blender.org/download/get-blender/
The compile is completing and creating an executable each time. I don't see any error messages on re-compiles. I'm going run the:
python scons\scons.py BF_TOOLSET=mingw clean
and let the compiler rip thru all of the code again. Not that I'm sure what to look for. It's so long and has so many warnings (is that normal??). I hate to ask about making it more verbose, but are there compiler, debug switches to turn on that might give me a clue?
I do not think you will have much luck compiling Blender 2.63 with Python 2.6.
-- Input devices for a 3D world.
Spacemice / Blender Compatibility
It compiled with 32-bit Python 2.6.6
I've uninstalled 2.6.6 and have installed 32-bit Python 2.7.3 and the pywin32 that goes with it. After cleaning the directories and doing a svn update:
python scons\scons.py BF_TOOLSET=mingw
Compiles like before. Crashes like before. Maybe 'crash' is giving it too much credit. Little seems to ever get started.
Just read something about "If you have Quicktime installed, Blender attempts to link with it on startup."
Is there anything else like that at startup? Is there a way to switch that off with the compiler config file?
Here I thought I might contribute to the debugging effort someday and I can't even get a compile of this thing to run.....
Still don't know where to look, but at least it's a different popup now.
Using 32-bit Python 2.7.3, win32-mingw, and scons.
Added a user-config.py:
|BF_BUILDDIR = 'C:\\BlenderSVN\\build\\win32-mingw'
BF_INSTALLDIR = 'C:\\BlenderSVN\\install\\win32-mingw'
BF_DEBUG = True
BF_NUMJOBS = 6
python scons\scons.py BF_TOOLSET=mingw
Build looks normal (I guess??):
C:\BlenderSVN\blender>python scons\scons.py BF_TOOLSET=mingw
scons: Reading SConscript files ...
BF_TOOLSET = mingw
No targets given, using default
Using config file: build_files\scons\config\win32-mingw-config.py
Using user-config file: user-config.py
Build with parallel jobs: 6
Build with debug symbols: True
~9900 lines later
C:\BlenderSVN\lib\mingw32\boost\include/boost/random/detail/integer_log2.hpp:71:35: warning: always_inline function might not be inlinable [-Wattributes]
Linking library ==> 'libextern_carve.a'
Linking library ==> 'libextern_ceres.a'
Linking program ==> 'blender.exe'
Linking program ==> 'blenderplayer.exe'
Install file: "C:\BlenderSVN\build\win32-mingw\bin\blenderplayer.exe" as "C:\BlenderSVN\install\win32-mingw\blenderplayer.exe"
Trying to remove existing py bundle.
Unpacking '../lib/mingw32/release/python32_d.tar.gz' to 'C:\BlenderSVN\install\win32-mingw\2.63\python\lib'
Install file: "C:\BlenderSVN\build\win32-mingw\bin\blender.exe" as "C:\BlenderSVN\install\win32-mingw\blender.exe"
scons: done building targets.
Well, I didn't want to go the Microsoft route, but what the heck, I've got a 32-bit compile with scons and Visual C++ 2008 Express working and the executable even runs!!
Mingw/scons still baffles me. Event log seems to blame libstdc++-6.dll.
|Application Error 2012-09-07T15:14:28.000000000Z
But honestly, I don't know what I'm looking at here.