@k1gen I added “return” just after the first line inside build() so that it wouldn't build again and simply pass through to package(). This allowed me to keep trying my package while making modifications to the PKGBUILD (such as correcting the SVG bit). Of course, it turns out that you can't use Unreal Engine plugins 3rd-party using any of this without adding in more code to add your project to it, just spews errors (not AUR fault, it's Unreal's fault). I ended up just going back to manual compiles and wrote a script to automate everything including adding my projects and such, I also use make -j32
and after it finally fails a make -j1
and it greatly speeds up my compilation. Unreal does a bad job of parallel-compilation.
Edit: I also use makepkg instead of using yay for big stuff like this. Git clone in the future, that way you can easily modify the package while testing first, at which case you then makepkg -s
to build, makepkg -i
to install. Can retry a lot easier.
Pinned Comments
Neko-san commented on 2022-11-01 02:32 (UTC) (edited on 2023-06-25 01:19 (UTC) by Neko-san)
@juancarlospaco this is easily done on your own system, not in a PKGBUILD, given that building packages runs as root:
Permission issues like this are already mentioned on the UE Arch wiki page: https://wiki.archlinux.org/title/Unreal_Engine_4#Installing_from_the_AUR
This is a user system problem; I already did what I could without needing users to do the above by giving the
777
permissions. If it still gives you trouble, you'll have to use the example to solve it or change the install location to somewhere you have user permissions by default (as I cannot do this for you).zerophase commented on 2021-05-27 08:15 (UTC) (edited on 2021-05-30 08:41 (UTC) by zerophase)
Will update to 5.0 when it is released.