| Git Clone URL: | https://aur.archlinux.org/blender-develop-git.git (read-only, click to copy) |
|---|---|
| Package Base: | blender-develop-git |
| Description: | Development version of Blender (non-conflicting version) |
| Upstream URL: | https://blender.org/ |
| Licenses: | GPL |
| Conflicts: | blender |
| Provides: | blender |
| Submitter: | bartus |
| Maintainer: | bartus |
| Last Packager: | bartus |
| Votes: | 12 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-05-04 01:47 (UTC) |
| Last Updated: | 2024-11-20 15:48 (UTC) |
After uninstalling, git cloning to its own folder & makepkg -si, it resulted in the same error.
Uninstalled again, cleared the pkg cache and any leftover files, reinstalled using yay, it's working now? I might have missed something during the first reinstall. Oh well. Regardless, thanks.
@MirandaStreeter: can't reproduce the issue. My build looks fine.
ldd /usr/bin/blender-2.8|grep vdb
libopenvdb.so.6.0 => /usr/lib/libopenvdb.so.6.0 (0x00007f6340265000)
Perhaps your aur helper has old cache. please build directly and check again.
@rigred After making the change, it compiles, But then when attempting to open, I'm seeing this error:
blender-2.8: error while loading shared libraries: libopenvdb.so.5.2: cannot open shared object file: No such file or directory
It looks like this may be related to openvdb having been updated to v6.0 recently? I'm not entirely sure if this is an issue upstream or if something was missed in the PKGBUILD.
For those wondering why it doesn't build anymore. Blender has moved the blender-2.8 branch into master as the active tree now. So in the PKGBUILD just change this line
source=('git://git.blender.org/blender.git#branch=blender-2.8' \
To this:
source=('git://git.blender.org/blender.git#branch=master' \
Until a 2.8 release is tagged/branched again this is the only solution.
Please update the master branch.
The master branch is now blender 2.8.
@bartus: I was unable to build Blender without llvm6-libs. But they had to fix it, because now it builds well.
@hugegameartgd: Can't help you, sorry. You should report bug upstream.
@nonoesimposible: When there is a straight beta release, for now we stays with rolling beta ;)...
Is Blender 2.8 Beta coming here soon?
Pinned Comments
bartus commented on 2020-01-16 16:01 (UTC) (edited on 2021-11-01 14:05 (UTC) by bartus)
Current packages state (non-conflicting ones):
bartus commented on 2019-04-10 11:40 (UTC) (edited on 2024-03-01 09:41 (UTC) by bartus)
Note: This is a non-conflicting version of blender-git package with GPU architecture detected at build time.
This package is also hosted on GitHub.
issuesandpatchesat GitHub.Use env vars to control the build process:
DISABLE_CUDA=1to skip cuda kernel build (cycles+compositor+optix,requires:cuda)DISABLE_HIP=1to skip amdgpu kernel build (requires:hip-runtime-amd)ENABLE_PYTHON_INSTALLinclude bundled python (default:off)DISABLE_NINJA=1to switch the build system to make (default:ninja)DISABLE_OPTIX=1to skip Optix device build.DISABLE_DRACO=1to skip gltf exporter draco mesh compression extension.FRAGMENT="#{commit,tag,branch}=..."for making bisect build.CUDA_ARCH="sm_xx sm_yy"to build for a specific Cuda arch, supports multiple values.HIP_ARCH="gfx900 gfx1103"to build for a specific amdgpu arch, supports multiple values.MAKEFLAGS="xxx"to override default make flags (check oom-killer disclaimer below)MAKEFLAGS="xxx:yyy"to override default make flags (colon-separated list)Usage cases:
export DISABLE_CUDA=1before buildDISABLE_CUDA=1 ~your-aur-helper~makepkg DISABLE_CUDA=1yay -S blender-develop-git --mflags "DISABLE_CUDA=1 DISABLE_HIP=1"Yayusers warning:Since yay relies solely on
aur-rpcto solve dependencies instead of callingmakepkg --syncit can't follow dependencies logic defined inPKGBUILD. That's why it's up to the user to provide dependencies to enable desired features. Optional features includes cuda/optix/usd.tl;dr; If you want to prebuild cycles kernels, you have to install CUDA beforehand. If you don't have CUDA installed,
PKGBUILDwill fail unless you disable cuda with DISABLE_CUDA=1, same for optix and usd.Out of memory killer.
You may use ninja-mem to prevent oom-killer when building on system with low memory to core ratio.
To activate use MAKEFLAGS+=" -m75" where 75 is the percentage upper threshold of memory usage when new build jobs is postponed.
Or simply lower the make jobs count in "MAKEFLAGS" variable, but this will prolong your build process.