Package Details: blender-develop-git 2.91.r98801.gb522e834ec3-1

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=2.91
Provides: blender=2.91
Submitter: bartus
Maintainer: bartus
Last Packager: bartus
Votes: 12
Popularity: 0.77
First Submitted: 2020-05-04 01:47
Last Updated: 2020-08-09 14:13

Dependencies (27)

Required by (52)

Sources (8)

Pinned Comments

bartus commented on 2020-01-16 16:01

Current packages state (non-conflicting ones):

bartus commented on 2019-04-10 11:40

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.
Use env vars to control build process:
  • DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor+optix)
  • DISABLE_NINJA=1 to switch build system to make (default:ninja)
  • DISABLE_OPTIX=1 to skip optix device build.
  • DISABLE_USD=1 to skip universal scene descriptor build.
  • FRAGMENT="#{commit,tag,branch}=..." for making bisect build.
  • CUDA_ARCH="sm_xx sm_yy" to build for a specific Cuda arch, supports multiple values.
  • MAKEFLAGS="xxx" to override default make flags (check oom-killer disclaimer below)
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"
Yay users warning:

Since yay relies solely on aur-rpc to solve dependencies instead of calling makepkg --sync it can't follow dependencies logic defined in PKGBUILD. 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, PKGBUILD will 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.

Latest Comments

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

bartus commented on 2019-10-22 09:04

@omgold: ok, I'll made one but it would be rether short lived PKGBUILD, as in a week blender 2.81 will land in arch/extra repo (after blender con I assume).

omgold commented on 2019-10-22 07:18

I would have a feature request. It would make sense, IMHO, to name the package and the installed files/dirs 2.81/2.82 instead of just *2.8. Currently blender has 3 versions of 2.8x, which people might want to have installed (2.80 stable, 2.81 beta and 2.82 alpha). Also in general it would be a good thing to allow installing multiple versions in parallel (as new versions tend to break old blend files).

kureta commented on 2019-10-21 08:22

@Humar if you are using yay you can run yay --gendb once and use yay -Syu --devel for system updates, instead of plain yay or yay -Syu. yay --gendb command will store hashes of current commits of your -git packages. yay -Syu --devel will check if any of those saved hashes have changed at the repo origin, meaning there is a new commit, then update if they have.

bartus commented on 2019-09-30 12:04

Nvidia optix backend landed in cycles.
  • Requires precompiled cuda kernel (cuda and optix installed)
  • You need a RTX Nvidia GPU.

bartus commented on 2019-08-26 16:12

Intels Open Image Denoise an AI base denoiser just landed in blender compositor.

bartus commented on 2019-04-10 11:40

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.
Use env vars to control build process:
  • DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor+optix)
  • DISABLE_NINJA=1 to switch build system to make (default:ninja)
  • DISABLE_OPTIX=1 to skip optix device build.
  • DISABLE_USD=1 to skip universal scene descriptor build.
  • FRAGMENT="#{commit,tag,branch}=..." for making bisect build.
  • CUDA_ARCH="sm_xx sm_yy" to build for a specific Cuda arch, supports multiple values.
  • MAKEFLAGS="xxx" to override default make flags (check oom-killer disclaimer below)
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"
Yay users warning:

Since yay relies solely on aur-rpc to solve dependencies instead of calling makepkg --sync it can't follow dependencies logic defined in PKGBUILD. 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, PKGBUILD will 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.

Humar commented on 2019-01-28 15:35

@bartus: I see, sorry!

I will maintain it myself then.

bartus commented on 2019-01-28 15:05

@Humar: You are supposed to rebuild -git packages regularly. I won't trigger a new version just because someone has an old build still lying around (ಠ_ಠ). New version for bugs only (° ͜ʖ°)

Humar commented on 2019-01-28 10:29

libboost_locale.so.1.68.0 is missing, because libboost is already on 1.69

MirandaStreeter commented on 2019-01-26 22:00

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.