Arch Linux User Repository

This package is also hosted on GitHub.

• Please report issues and patches at: https://github.com/bartoszek/AUR-blender-git
• CI Build Status: <img alt="Build Status" src="https://travis-ci.org/bartoszek/AUR-blender-git.svg?branch=travis" />

Use env vars to control build process:

• 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:

• makepkg CUDA_ARCH=sm_52
• yay -S blender-git --mflags "CUDA_ARCH=sm_52"

Optional features, defined at build time base on installed packages:

• cuda
• usd
• aur/optix
• openimagedenoise

Disclaimer:

If you want to prebuild cycles/compositor kernels, you have to install cuda beforehand. If you don't have cuda installed, PKGBUILD will silently discard cycles/compositor cuda kernel build.

Same goes with usd,optix,openimagedenoise features.

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 bear in mind this will prolong your build process.

@carlosnewmusic Use MAKEFLAGS to reduce memory assignment. This is mostly described below.

Less threads or just a specific cuda kernel solves that issue. The kernels consume around 3GB RAM each.

when compiling it leaves the system frozen using all available ram and swap

@bartus Don't know the exact reason, but PKGBUILD was stuck to some older version: pkgver=2.93.r103953.gbc851700a61 which did not yet had the extra opt paths.

Even after deletion of PKGBUILD it was recreated with that older version. Maybe some AUR helper bug (yay).

A clean build helped.

I had installed the qfix-packages manually before updating blender-git so i did not realize the old PKGBUILD.

Sorry and thanks for helping!

There are other problems and i will open an issue at github.

This package is also hosted on GitHub.

• Please report issues and patches at: https://github.com/bartoszek/AUR-blender-git
• CI Build Status: <img alt="Build Status" src="https://travis-ci.org/bartoszek/AUR-blender-git.svg?branch=travis" />

Use env vars to control build process:

• 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:

• makepkg CUDA_ARCH=sm_52
• yay -S blender-git --mflags "CUDA_ARCH=sm_52"

Optional features, defined at build time base on installed packages:

• cuda
• usd
• aur/optix
• openimagedenoise

Disclaimer:

If you want to prebuild cycles/compositor kernels, you have to install cuda beforehand. If you don't have cuda installed, PKGBUILD will silently discard cycles/compositor cuda kernel build.

Same goes with usd,optix,openimagedenoise features.

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 bear in mind this will prolong your build process.

@sausix: Strange, as I explicitly popped up pkgrel for openshadinglanguage-qfix to trigger rebuild ( ಠ ʖ̯ ಠ) ###

Also weird, that cmake fails to find oiio since it has direct path to oiio provided in -DOPENIMAGEIO_ROOT_DIR=/opt/oiio switch. ###

Could you please add --trace-expand to cmake call and check blender-git-*-build.log for FindOpenImageIO.cmake lines.

##patch

Apply with git apply -v <(curl -s http://ix.io/2QiQ) in blender-git clone.

To get blender-git*-build.log build with makepkg -L

Then search for those lines blender-git*-build.log :

...
/build/blender-git/src/blender/build_files/cmake/Modules/FindOpenImageIO.cmake(42):  FIND_LIBRARY(OPENIMAGEIO_LIBRARY NAMES OpenImageIO HINTS /opt/oiio;/opt/lib/oiio PATH_SUFFIXES lib64 lib )
...
/usr/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake(480):  string(APPEND DETAILS [/opt/oiio/lib/libOpenImageIO.so] )
...

btw. If you want to post blender-git*-build.log use ix.io

Thanks for previous fixing!

openshadinglanguage-qfix was not updated/triggered somehow and still provided /usr/bin/oslc which was not working anymore because of newer libclang-cpp.so.

After forcing a reinstall of all your *-qfix packages, it seems like that blender-git does not find the libs in the new destinations below /opt.

CMake Error at CMakeLists.txt:926 (message):
  Cycles requires WITH_OPENIMAGEIO, the library may not have been found.
  Configure OIIO or disable WITH_CYCLES

@sausix: This is due to conflict between open{image,color}io witch was rebuild using different version ( openimageio<-opencolorio1 not opencolorio=2 )

Should be fixed now ( using openimageio-qfix since community/openimageio get rebuild against opencolorio=2 )

For any reason the dependency opencolorio always wants to replace any preinstalled opencolorio or opencolorio-git into opencolorio1 which results in:

-- Could NOT find OpenColorIO: Found unsuitable version "1.1.1", but required is at least "2.0.0" (found /usr/lib/libOpenColorIO.so;/usr/lib/libyaml-cpp.so;/usr/lib/libexpat.so;/usr/lib/libpystring.so)

And that removes color management completely except basic RGB.

What's the cause of this problem?

Found it. openimageio requires and pulls opencolorio1.

With openimageio-git:

/usr/bin/oslc: error while loading shared libraries: libOpenImageIO.so.2.2: cannot open shared object file: No such file or directory

I'm giving up.

"error merging blender-git: fatal: No current branch."

@sausix I would say outdated

Feel free to report ;)