On Thu, Nov 4, 2010 at 9:37 AM, Dave Plater <[email protected]> wrote: > On 11/04/2010 12:33 AM, Campbell Barton wrote: >> On Wed, Nov 3, 2010 at 1:09 PM, Dave Plater <[email protected]> wrote: >> >>> On 11/02/2010 11:02 PM, Dan Eicher wrote: >>> >>>> Been seeing some weirdness on recent builds on Ubuntu 10.10 x86_32. >>>> >>>> The menu bar doesn't show up like the OP and if I try to resize a window >>>> (mouse over the border until the double arrows show up) as soon as I start >>>> to move it the top header jumps to the mouse position. >>>> >>>> If I open older .blend files everything works as expected. >>>> >>>> 99% sure r32757 is the cause, reverting that and everything works fine. >>>> >>>> Dan >>>> >>>> >>>> >>> Thanks, I'm building 2.54, which I never finished due to windowmanager >>> not finding BPY_extern.h. Busy tying to add the neccesary -I flag, >>> couldn't add it via $CFLAGS so I'll have to patch the relevant >>> CMakeLists.txt. If I have a sucessful 2.54 build I can work forwards to >>> find the problem. Also fighting with kdevelop3 which freezes when I load >>> blender project. >>> Dave P >>> >> Undid most changes from r32757, Can you test r32861? Dan says its >> working now, not sure why this worked for me but broke elsewhere. >> >> > Ok, I had a feeling that a problem like this would be a system or build one. > Eureka, I just started to gdb blender, the debugging source is packaged > and installed as a separate rpm. > I looked up "BPy_init_modules( void )" in kdevelop3, using the patched > sources that are used to build and tried to enter a break on "bpy.c:179" > and gdb couldn't find it. > So I looked in "find /usr/src/debug/blender-2.55.32862/ -name bpy.c" and > it doesn't exist. > This must be a result of the " -DWITH_PYTHON:BOOL=off" statement. I will > examine build logs and play around a bit to see what I can find but this > is a bug, you at least need to put a warning. > What are " -DWITH_PYTHON:BOOL=off" and "-DWITH_PYTHON_INSTALL:BOOL=off" > actually supposed to do? I'm trying to build blender using systems > python3 which combination of the two flags would I need. > "OPTION(WITH_PYTHON_INSTALL "Copy system python into the blender > install folder" ON)" I take this to mean that the systems python3 will > be packaged with blender. > > "OPTION(WITH_PYTHON "Enable Embedded Python API" ON)" This I > think is the equivalent to scons's "WITHOUT_BF_PYTHON_INSTALL: dont > install Python modules if true (yes|no)" . > > So the reason for strace not picking up the scripts loading is because > there wasn't a bpy.c to find it. > I'm building with " -DWITH_PYTHON:BOOL=on" and > "-DWITH_PYTHON_INSTALL:BOOL=off" I think I had a build failure when I > tried it before. > Will report back. > Dave P
WITH_PYTHON needs to be enabled otherwise you loose almost all of blenders UI. I'll add a waring on startup for builds with python disabled so this doesn't happen again, this is only kept for testing/debugging purposes. WITH_PYTHON_INSTALL is only for our own portable bundles to avoid relying on the systems python which proved problematic in the past - having to support multiple versions. If the distribution has a python3.1 package that blender depends on then this isn't needed. Also noticed yafray is listed as a dependency in the spec file you linked with, this can be removed. -- - Campbell _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
