| 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: | 14 |
| Popularity: | 0.000004 |
| First Submitted: | 2018-05-11 21:03 (UTC) |
| Last Updated: | 2025-04-28 09:06 (UTC) |
@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
@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
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')
The package is patches (0013-spdlog.patch) to use system spdlog instead of the included one, but spdlog is missing from the dependencies, which leads to the build failing if spdlog is not installed.
This packet currently depends on openimageio, but ships it's own openimageio.a library, doesn't seem right.
@DarkShadow44: well I could regenerate .SRCINFO with DISABLE_CUDA=1 and add disclaimer for yay users that they need to ma manually install cuda or include --margs=DISABLE_CUDA=1 switch in yay call to skip the cuda kernel build, same as I already did for blender-develop-git.
Btw. Paru has this covered, instead of relying on the static .SRCINFO it regenerate it on each build ¯\_(ツ)_/¯
@bartus The dependency is still fetched, and cuda is pretty huge. AFAIK that's a known problem with yay.
@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?
I noticed you can't disable cuda build with yay. Any idea how to fix that?
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.
issuesandpatchesat GitHub.Use env vars to control build process:
DISABLE_OPENCL=1to skip opencl kernel build (yields DISABLE_CUDA=1)DISABLE_CUDA=1to skip cuda kernel build.Usage cases:
export DISABLE_CUDA=1before buildDISABLE_CUDA=1 ~your-aur-helper~makepkg DISABLE_CUDA=1yay -S blender-2.8-git --mflags "DISABLE_CUDA=1"bartus commented on 2019-04-10 11:42 (UTC)
Please report
issuesandpatchesto luxcorerender@github.com