waebbl / waebbl-gentoo

Personal overlay of gentoo ebuilds, loosely focused on the 3D domain.
17 stars 17 forks source link

media-gfx/luxcorerender-2.4: version bump #294

Open nick87720z opened 3 years ago

nick87720z commented 3 years ago

Besides very fact, that newer release is available (2.4 is since this jul, while 2.1 is since Jan 2019), I suppose that later versions could support later python versions - 3.7 and higher.

Besides that there are questions. I tried simplest bump in my local overlay, also adding python 3.7 for test if it will work. But there are some unclear deps. media-libs/embree slot: is it right that all versions (up to 3.12* if it was packaged) are ok? I have another repo enabled - "cg", which assigns slot "3" for its version 3.11, while your has "0" (as if from vim default).

waebbl commented 3 years ago

I'm aware of the new release and in fact started to bump the ebuild sometime in late summer or autumn last year. I think you're right with supporting later python versions, they require at least python-3.4 according to their cmake files.

However, there are some issues, beside low time ressources during the second half of the last year. The upstream build system seems not very distribution agnostic, at least for the outdated version that's still in my repo (might have changed since), so there might be a need of some hacking, to get it built successfully for Gentoo.

As for your questions. Upstream doesn't have any version specification when searching for embree, so all versions should be supported. My latest embree is 3.5.2, which is also outdated. I don't know the reason, why 'cg' added a new slot to his ebuilds. He has some interesting ebuilds, but is not always following the Gentoo rules down to the word. On "redchillipadi" overlay, there's also an ebuild for 3.12.1 which uses slot 0. Usually slot 0 is the default, and other slots can be used, whenever different versions can be installed together, which I doubt is the case for embree (but I haven't checked this).

I'm currently working on updating another package, which takes time, due to many USE flags and long build times, so it can take some more time, before I come back to this package, but I want to update it anyway.

nick87720z commented 3 years ago

Found this issue: https://github.com/LuxCoreRender/LuxCore/issues/217 Looks like all luxcorerender is broken by boost upgrade, at least for me it fails to find all boost libs. What's interesting, when built by ebuild it gives this in log:

Could NOT find Boost (missing: python-3.6) (found suitable version "1.74.0", minimum required is "1.56.0")

Despite -DPYTHON_INCLUDE_DIR and -DPYTHON_LIBRARY have correct values. While for manual build it's a bit different:

Could NOT find Boost (missing: python numpy) (found suitable version "1.74.0", minimum required is "1.56.0")

Btw, boost has numpy use flag, which is not in requirement (if only it could make boost found). This requires boost upgrade to unstable r2, because r1 has it masked.