The comments: -----8<--------- And here it is, finally! In short; we now have raytracing, soft shadows, area light, mesh beveling, displacement mapping, python import/export menus, and... Yafray integrated support! And that's not all... check here the many many pages with release notes: http://www.blender.org/docs/2.32_release/release232.html And of course: Yafray 0.0.6: http://download.blender.org/release/yafray.0.0.6/ -----8<--------- Like you can see it need yafray 0.0.6. Yafray must be a dependence of blender>=2.32 I hope to see a ebuild soon ! -pol-
I cannot find the sources. I successfully build yafray-0.0.6 so I could commit it now
Source is the same place as the last versions: http://download.blender.org/source/blender-2.32.tar.bz2
yesterday wasn't I'm fetching it now at most tomorrow the ebuild will be in portage
For those in a hurry: --- /usr/portage/media-gfx/blender/blender-2.31a.ebuild 2003-12-07 10:40:49.000000000 +0100 +++ blender-2.32.ebuild 2004-02-03 18:04:51.000000000 +0100 @@ -15,7 +15,7 @@ SLOT="0" LICENSE="GPL-2 | BL" -KEYWORDS="~x86 ~ppc ~amd64" +KEYWORDS="x86 ~ppc ~amd64" DEPEND="virtual/x11 blender-game? ( dev-games/ode ) @@ -28,12 +28,14 @@ >=media-libs/openal-20020127 >=media-libs/libsdl-1.2 >=media-libs/libvorbis-1.0 - >=dev-libs/openssl-0.9.6" + >=dev-libs/openssl-0.9.6 + >=sys-devel/automake-1.7.9" src_unpack() { unpack ${A} epatch ${FILESDIR}/configure-fix-${PV}.patch epatch ${FILESDIR}/${P}-plugins.patch + epatch ${FILESDIR}/${P}-build.patch cd ${S}/release/plugins chmod 755 bmake } cat files/blender-2.32-build.patch --- blender-2.32/source/blender/blenlib/Makefile.am.old 2004-02-03 17:36:04.802732024 +0100 +++ blender-2.32/source/blender/blenlib/Makefile.am 2004-02-03 17:37:46.203316792 +0100 @@ -47,7 +47,8 @@ INCLUDES = -I$(top_srcdir)/source/blender/makesdna \ -I$(top_srcdir)/intern/guardedalloc \ - -I$(top_srcdir)/source/blender/include + -I$(top_srcdir)/source/blender/include \ + -I$(top_srcdir)/source/blender/blenkernel EXTRA_DIST = \ Makefile \ Plus support for yafray, of course. Didn't need it. Oh, and autmake-1.7.9 isnt in portage yet, but it was a simple version bump from the 1.7.8-ebuild for me.
I did not need a newer version of automake, could you tell me why it is needed?
I think we should use the new scons build engine ... what do you think ?
Hm, on my pc, the compile stopped somewhere down with "automake: file is from 1.7.9, but installed version is 1.7.7", and I found no way around it. Did you need the build patch I used? (looked myself, seems like you did). Did you use 1.31a.ebuild as your starting point? Did you have all use flags set (except static), as I did? Other than that, I have no idea what could be the difference.
could you check if the ebuild in portage works for you?
Now I'm puzzled - it works, with automake-177