Package Details: unreal-engine 5.4.2-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: 74
Popularity: 0.84
First Submitted: 2016-05-01 18:37 (UTC)
Last Updated: 2024-06-17 03:29 (UTC)

Required by (1)

Sources (5)

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 .. 74 75 76 77 78 79 80 Next › Last »

madsciencecoder commented on 2016-05-14 22:58 (UTC)

I'm having a similar problem as zerophase. The editor opens but when I try to open a code project it closes and a pop up says "The following modules are missing or built with a different engine version: libUE4Editor-MyProject.so". The part after the hyphen matches the name of the project. It then asks if I'd like to rebuild it which fails if I click yes.

zerophase commented on 2016-05-14 15:41 (UTC)

I'm just trying to figure out why the editor keeps crashing while generating code projects.

acerix commented on 2016-05-12 23:24 (UTC)

I fixed the patch, I had the arguments in the wrong order. I didn't need to remove ld.gold to build this, so I skipped that part. But I don't really know what that does exactly, it may still apply to other Unreal builds.

zerophase commented on 2016-05-12 23:19 (UTC)

Hey, is removing ld.gold from Clang still required for Unreal code projects?

zerophase commented on 2016-05-12 15:34 (UTC) (edited on 2016-05-12 18:52 (UTC) by zerophase)

@acerix The only thing with adding Linux patches upstream is Epic seems to take a very long time to integrate them into their code base. Some patches for cmake support have been waiting for months with little activity on Epic's part. Whenever I run makepkg -sri I keep getting "patch: **** Only garbage was found in the patch input."

acerix commented on 2016-05-12 00:48 (UTC) (edited on 2016-05-12 00:56 (UTC) by acerix)

@corrupt I applied your patch, it's a good fix for now, maybe it will be fixed upstream in the next release. I replaced $startdir which is deprecated. @recured I haven't read the entire license, so I'm not sure distributing the compiled version is allowed, although I figure it should be. Assuming it is, I would upload it, but I've used too much bandwidth just making this package that I can't spare 20 GB more this month. If you have a decent PC, it should only take an hour or so to build.

recured commented on 2016-05-11 16:09 (UTC)

Is there any chance of this getting a pre-built release? It just seems like too much to compile

corrupt commented on 2016-05-09 18:26 (UTC)

It seems it's general practice to fill conflicts for such cases. Maybe you have clang in pacman.conf's ignore or noupgrade. PKGBUILD has package checks. It's bad(for UE devs) to run pacman in setup script like that. They should have left it in wiki.

acerix commented on 2016-05-09 17:43 (UTC)

Thanks, for some reason I don't get that prompt, but it should be fixed. I'm thinking it would be better to add "provides=(clang)" to the clang35 package though, that way it would still allow building with the latest clang (even though it's not working yet) and I prefer to avoid patches since they need to be maintained.

corrupt commented on 2016-05-09 17:26 (UTC) (edited on 2016-05-09 17:30 (UTC) by corrupt)

Yes, clang is newer package than clang35 and it prompts to update to newer version (and fails). This is minimal change for it to build. Removing also works. Have not tried to build with current clang to confirm.

« First ‹ Previous 1 .. 74 75 76 77 78 79 80 Next › Last »