| 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-12-09 15:16 (UTC) |
@berilac: You have some point here. I can go two ways here: make it non-conflicting with blender-git by renaming /usr/share/bledner/2.83/, or explicitly add blender-git as conflict...
I think I'll choice the later, as having both blender-git and blender-2.8-git` seems redundant to me. 69ad5501effd
Am I right in saying that this package conflicts with blender-git (given it's not in the pinned list)? (https://aur.archlinux.org/packages/blender-git/)
Also, blender-git is now compiling 2.83, so is fighting over ownership of /usr/share/blender/2.83
Thanks, it works now again. But please change this in PKGBUILD:
- chmod 444 "$pkgdir/usr/share/blender/${_suffix}/scripts/addons/cycles/lib/*"
+ chmod 444 -R "$pkgdir/usr/share/blender/${_suffix}/scripts/addons/cycles/lib/"
Without this patch I got an error that file is not found.
I currently have this issue when compiling: https://github.com/bartoszek/AUR-blender-2.8-git/issues/7
@Canseco: Already working on it, there's some problem with linking binaries boost_python27 is missing, Here's a wip repo.
Since Blender 2.82 there's a new dependency, Universal Scene Description. Could it be possible to add this in the future?
Current packages state (non-conflicting ones):
Now we have again the 'multiple versions of interest' situation as of recently:
Might it be possible to get packages set up such that all of these can be installed concurrently?
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.