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: howetuft
Votes: 15
Popularity: 0.009068
First Submitted: 2018-05-11 21:03 (UTC)
Last Updated: 2024-01-31 15:18 (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 »

DarkShadow44 commented on 2022-03-20 17:27 (UTC)

@bartus The dependency is still fetched, and cuda is pretty huge. AFAIK that's a known problem with yay.

bartus commented on 2022-03-20 06:30 (UTC) (edited on 2022-03-20 06:33 (UTC) by bartus)

@DarkShadow44

As far as I can tell it should work.

Cmake flags are defined in the PKGBUILD scrip.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=luxcorerender#n14

Logic is present in the LuxCoreRender Cmake script.

https://github.com/LuxCoreRender/LuxCore/blob/master/CMakeLists.txt#L143-L158

Did you mean the cuda is still fetched as dependency, or that cuda kernel is build despite adding --margs=DISABLE_CUDA=1 to the yay call?

DarkShadow44 commented on 2022-03-19 17:52 (UTC)

I noticed you can't disable cuda build with yay. Any idea how to fix that?

neo2001 commented on 2022-03-08 13:07 (UTC)

This is just a note for everyone maybe having the same issue:

$ luxcoreui
LuxCoreUI v2.6 (LuxCore demo: http://www.luxcorerender.org)
GLFW Error: 65544
Description: Wayland: Failed to connect to display

Although I don't use Wayland, Octopi/yay installed glfw-wayland instead of glfw-x11 and LuxCoreUI wouldn't start. After replacing gflw-wayland with gflw-x11 everything worked fine again.

This maybe a configuration issue on my side, so I put this out just FYI.

gardotd426 commented on 2021-10-14 13:59 (UTC)

I have no idea why that comment duplicated, I've been seeing that lately on this site.

bartus commented on 2021-10-14 11:45 (UTC)

@gardot: Fixed, forgot to push GitHub PR to AUR again, now everything is synced.

btw. could you please concat duplicated comments, thansk.

bartus commented on 2021-10-14 11:22 (UTC)

@gardot: Yep, need to port some changes from the master branch until fixed I'll suggest using luxcorerender-git package which is openexr:3 compatible.

btw. please remove duplicated comment.

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