On 11/04/2010 12:43 PM, Campbell Barton wrote: > 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 As you might have seen from my previous message, it was -DWITH_PYTHON=no that caused quote "you loose almost all of blenders UI" my problem. At least I've learned a lot about blenders internals which are quite different to the qt and gtk ui's that I'm used to. Such a bug as mine has to be something stupid and obvious enough to get missed. One of my builds, I think the first 2.55 one failed with "-DWITH_PYTHON=yes" and "-DWITH_PYTHON_INSTALL=no" otherwise I would have caught it a while ago. I can now push blender-2.55.32862 through to the future 11.4. I'll remove yafray and the package will benefit from the spec file clean up that's resulted from this. Are the sequence and texture plugins still used or can I remove them as well, if so will there still be includes and headers that need to be packaged? Also there are extra icons under freedesktop that aren't installed, what are they for? btw the with player build succeeded. Dave P
_______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers