| Git Clone URL: | https://aur.archlinux.org/blender-2.83-git.git (read-only, click to copy) |
|---|---|
| Package Base: | blender-2.83-git |
| Description: | LTS Maintenance version of blender-v2.83-release branch |
| Upstream URL: | https://blender.org/ |
| Licenses: | GPL |
| Conflicts: | blender |
| Provides: | blender |
| Submitter: | bartus |
| Maintainer: | bartus |
| Last Packager: | bartus |
| Votes: | 2 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-05-04 00:28 (UTC) |
| Last Updated: | 2024-03-23 23:16 (UTC) |
The required package usd=19.11 is no longer available in the repositories, causing the build to fail early. Unfortunately, the current version usd=20.11-4 is not compatible and the build fails during compilation of source/blender/io/usd/CMakeFiles/bf_usd.dir/intern/usd_writer_mesh.cc.o.
Maybe the simplest solution is to create an aur package of usd-19.11 and add this as source.
@bartus: nice, thanks. That helps
@berilac: btw. you can see the difference when you do stuff like this: https://repl.it/@bartoszek/MidnightbluePopularApplications#main.sh
@bartus: very much appreciated, and sorry for the trouble.
@berilac: there are two distinct expansion of array in bash, @ and *. First preserves White spaces, second don't. https://repl.it/@bartoszek/MidnightbluePopularApplications#main.sh
@bartus: Right, looks like bash requires slightly different syntax for the expansion.
echo "${_SOME_VAR[@]}"
So my bad, the variables should have been set fine, and I was just not echoing them out properly :/ Sorry
@bartus: https://repl.it/repls/MidnightbluePopularApplications Horribly simple.
@berilac: could you perhaps post your test script to repl.it so I can look into it?
@bartus: It intrigued me as well. Just ran quick bash script test. Same issue. only gets set first time, and also if more than one item is in the list the first time, only the first is stored.
...OK, it looks like bash and sh do not do what we expect, but zsh does.
@bartus: only that the arrays were seemingly not expanding at all, after the first on line 13.
I have no idea why. I'm trying to read around the topic to see if it's something in my system config.
Pinned Comments
bartus commented on 2022-03-14 10:30 (UTC)
Sorry lads, I'm at the Polish Ukraine border helping allocate refugees. Expect no update until this hell is over, wish us luck. Have no time nor access to my rig and AUR keys to test/post updates. If you have a patch, ping me on email - I'll add you as co-maintainer. Posted with my old script - https://github.com/bartoszek/aur-post
bartus commented on 2021-05-05 08:05 (UTC)
Note: This is a non conflicting version of blender-git package tracing
blender-v2.83-maintnancebranch for blender:2.83 LTS relaease with GPU architecture detected at build time.This package is also hosted on GitHub.
issuesandpatchesat GitHub.Use env vars to control build process:
DISABLE_CUDA=1to skip cuda kernel build (cycles+compositor+optix)DISABLE_NINJA=1to switch build system to make (default:ninja)DISABLE_OPTIX=1to skip optix device build.DISABLE_USD=1to 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=1before buildDISABLE_CUDA=1 ~your-aur-helper~makepkg DISABLE_CUDA=1yay -S blender-2.8-git --mflags "DISABLE_CUDA=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.