Package Details: unreal-engine 5.4.4-0

Git Clone URL: https://aur.archlinux.org/unreal-engine.git (read-only, click to copy)
Package Base: unreal-engine
Description: A 3D game engine by Epic Games which can be used non-commercially for free.
Upstream URL: https://www.unrealengine.com/
Keywords: 3D engine game ue5 Unreal
Licenses: GPL3, custom:UnrealEngine
Submitter: acerix
Maintainer: Shatur (Neko-san)
Last Packager: Neko-san
Votes: 75
Popularity: 0.63
First Submitted: 2016-05-01 18:37 (UTC)
Last Updated: 2024-09-04 18:39 (UTC)

Required by (1)

Sources (6)

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:

sudo groupadd unrealengine-users
sudo usermod -aG unrealengine-users (your-username)
sudo chown -R root:unrealengine-users /opt/unreal-engine
sudo chmod -R 775 /opt/unreal-engine

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.

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 81 Next › Last »

Tio commented on 2022-07-09 16:08 (UTC)

Cannot build it:

==> ERROR: You must register at unrealengine.com and link your github account to access this private repo. See the wiki for more info: https://wiki.archlinux.org/index.php/Unreal_Engine_4
Failed to build unreal-engine

Neko-san commented on 2022-07-07 02:55 (UTC)

@Shatur You say that, but I've actually rm -rf'd my root folder with makepkg through a bug before Lol

I never reported that bug though, because I didn't want to have to re-check exactly how I did it and put myself through that hell again just to confirm the exact working example

Shatur commented on 2022-07-06 06:42 (UTC)

Yes, you can't modify the filesystem outside of the PKGBUILD.

Neko-san commented on 2022-07-06 04:49 (UTC)

I find it odd that ln had a permission denied issue when makepkg is supposed to have elevated privileges?

poptrek commented on 2022-07-05 18:49 (UTC) (edited on 2022-07-05 19:09 (UTC) by poptrek)

ln: failed to create symbolic link '/usr/lib/ssl': Permission denied

Tried with both yay and manual

Update: Did these two steps manually and edited PKGBUILD file and its working so far

Neko-san commented on 2022-07-05 06:31 (UTC)

I've made ab attempt to fix the NuGet ussue; I'll attempt the env variable next if this doesn't work.

Let me know if you encounter this again; I kind of have some stuff going on, so I won't be able to test this (especially since I don't experience this problem)

Azzunyan commented on 2022-07-04 11:20 (UTC)

I solved this problem on Fedora by adding an environment variable DOTNET_SYSTEM_NET_HTTP_USESOCKETSHTTPHANDLER=0

xaperret commented on 2022-07-03 17:27 (UTC)

@Neko-san I've tried what you mentionned below (with makepkg) but I have the same exact error as @doskanoness and I'm pretty sure that 1) and 2) are not a problem.

...
./v20_clang-13.0.1-centos7/x86_64-unknown-linux-gnu/usr/lib64/libnsl.a

Target arch set to: x86_64-unknown-linux-gnu
Building ThirdParty libraries

If you don't see SUCCESS message in the end, then building did not finish properly.
In that case, take a look into /home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Build/BatchFiles/Linux/BuildThirdParty.log for details.

No third party libs needed to be built locally

**********  SUCCESS ****************
Setup successful.
==> Starting build()...

Running AutomationTool...

Fixing inconsistent case in filenames.
Setting up Mono
Setting up bundled DotNet SDK
Rebuilding: AutomationTool assembly not found
/home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Binaries/ThirdParty/DotNet/Linux/sdk/3.1.401/NuGet.targets(255,5): error : Unable to load the service index for source https://api.nuget.org/v3/index.json. [/home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Source/Programs/AutomationTool/AutomationTool.csproj]
/home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Binaries/ThirdParty/DotNet/Linux/sdk/3.1.401/NuGet.targets(255,5): error :   The SSL connection could not be established, see inner exception. [/home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Source/Programs/AutomationTool/AutomationTool.csproj]
/home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Binaries/ThirdParty/DotNet/Linux/sdk/3.1.401/NuGet.targets(255,5): error :   The remote certificate is invalid according to the validation procedure. [/home/xavierp/Downloads/unreal-engine/src/unreal-engine/Engine/Source/Programs/AutomationTool/AutomationTool.csproj]
Compilation failed
RunUAT ERROR: AutomationTool failed to compile.
==> ERROR: A failure occurred in build().
    Aborting...

Premik commented on 2022-07-01 07:59 (UTC)

@doskanoness Unable to load the service index for source. Isn't this the NuGet cert issue mentioned few pages below? If so either symlink the system certs or import the anchors to the user storage.

Neko-san commented on 2022-07-01 07:36 (UTC) (edited on 2022-07-01 07:37 (UTC) by Neko-san)

@doskanoness I'm not entirely certain of this issue but it appears as though something's happening here that doesn't look like it should be the case...

It calls the Automation Tool, which looks like it's running, until it suddenly decides it's missing something then stops...

A few questions: 1) you should have been prompted by two or three SSH passphrase prompts, did you enter all of them? 2) Are you sure you had enough storage space for the mono dependencies and didn't run out? 3) If yes to both of the prior, try using makepkg and see if it happens again instead of yay; I've had this same version tested the other day with makepkg and it wasn't a problem, so I'd like to see if that's consistent for you