Package Details: luxcorerender 2:2.7.beta1-2

Git Clone URL: https://aur.archlinux.org/luxcorerender.git (read-only, click to copy)
Package Base: luxcorerender
Description: Physically correct, unbiased rendering engine.
Upstream URL: https://www.luxcorerender.org/
Licenses: Apache
Provides: luxrays
Submitter: bartus
Maintainer: bartus (howetuft)
Last Packager: bartus
Votes: 15
Popularity: 0.000077
First Submitted: 2018-05-11 21:03 (UTC)
Last Updated: 2024-11-25 20:46 (UTC)

Dependencies (21)

Sources (15)

Pinned Comments

bartus commented on 2020-06-11 15:32 (UTC) (edited on 2020-08-22 09:39 (UTC) by bartus)

This package is also hosted on GitHub.
Use env vars to control build process:
  • DISABLE_OPENCL=1 to skip opencl kernel build (yields DISABLE_CUDA=1)
  • DISABLE_CUDA=1 to skip cuda kernel build.
Usage cases:
  • export DISABLE_CUDA=1 before build
  • DISABLE_CUDA=1 ~your-aur-helper~
  • makepkg DISABLE_CUDA=1
  • yay -S blender-2.8-git --mflags "DISABLE_CUDA=1"

bartus commented on 2019-04-10 11:42 (UTC)

Please report issues and patches to luxcorerender@github.com

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

MarsSeed commented on 2023-08-05 10:23 (UTC)

Though luxcorerender is only a makedepend of luxmark, and in that capacity it functions just fine.

MarsSeed commented on 2023-08-05 10:21 (UTC)

@howetuft, the Python 3.11 and boost linking problem was resolved.

But luxmark is broken for other reasons, unfortunately.

I did not test luxcorerender in any other way (e.g., with Blender).

howetuft commented on 2023-06-14 17:54 (UTC)

@MarsSeed sorry, I was away from my computer, I did not notice your answer. You asked for some help about a Python 3.11 linking issue in Luxmark, but I understand that it has been fixed by DarkShadow44, am I right?

DarkShadow44 commented on 2023-06-10 17:14 (UTC)

Thanks for the update, I fixed the luxmark part and it now works.

MarsSeed commented on 2023-06-10 10:25 (UTC)

Btw do you have any suggestion what could cause a new linking failure with Python 3.11 in luxmark? See this comment.

(You have to disable LTO for luxmark build as well, it has not been added to its PKGBUILD. If LTO is enabled for luxmark, it will still have linking errors - undefined references - for luxcorerender / luxrays.)

(I have tested every combination wrt LTO. Only when both luxcorerender and luxmark have LTO disabled eliminates linking issues between the two. But unfortunately there is this new Python linking error via Boost libs.)

MarsSeed commented on 2023-06-10 10:19 (UTC) (edited on 2023-06-10 10:19 (UTC) by MarsSeed)

@howetuft thanks for the changes.

I have proof that you cannot not have build problems with having embree (v4) instead of embree3. :)

See the cmake find definition explicitly seeking embree3 in luxcorerender v2.6:

https://github.com/LuxCoreRender/LuxCore/blob/luxcorerender_v2.6/cmake/Packages/FindEmbree.cmake

howetuft commented on 2023-06-10 10:01 (UTC)

@MarsSeed Removed link time optimization as requested. Also swapped embree for embree3, although I did not personally encountered any build failure with embree 4. Please confirm it's ok for you

MarsSeed commented on 2023-06-06 17:57 (UTC)

And also LTO needs to be explicitly disabled in PKGBUILD, otherwise linking will fail when building packages that depend on this.

See this comment on luxmark AUR page.

Please kindly add the following field attribute to the header section of the PKGBUILD:

options=('!lto')

MarsSeed commented on 2023-06-06 15:31 (UTC)

Build fails.

Current version of LuxCoreRender, 2.6, depends now on embree3, not on embree whose main version is v4.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »