Package Details: unreal-engine 5.5.0-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: 76
Popularity: 1.03
First Submitted: 2016-05-01 18:37 (UTC)
Last Updated: 2024-11-16 03:10 (UTC)

Dependencies (29)

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 .. 17 18 19 20 21 22 23 24 25 26 27 .. 81 Next › Last »

Neko-san commented on 2022-11-18 05:51 (UTC) (edited on 2022-11-18 05:56 (UTC) by Neko-san)

@fhajii Sorry about that, I might've been half-asleep when I typed out line 194 and I had forgotten to correctly write that install statement; I just corrected the PKGBUILD to account for this

Your current state is recoverable but doing so might be a bit odd; from line 194 going forward in the PKGBUILD (reference the new file for doing this), you can run these same commands (almost) as-is (cd into unreal-engine and use ../pkg instead of ${pkgdir} instead) in your terminal and finish the file organization setup

However, you'll also need to compress the contents of your pkg folder into a pacman archive (.pkg.tar.zst) as well if you want the package to be installed by pacman

Otherwise, you can just move its contents to where you want it to be installed and it should work just fine as-is but doing that won't have it tracked by your package manager

If for whatever reason you can't adapt the rest of the script from line 194 going forward (in the event you don't understand it), I'd advise just having it re-compile overnight and have it automate it for you

fhajji commented on 2022-11-18 05:31 (UTC)

Build 5.1.0-0 successful, but then this happens:

Saving file list to /opt/yay/unreal-engine/src/unreal-engine/Engine/Saved/BuildGraph/Make Installed Build Linux/Tag-Make Installed Build Linux.xml
Saving file list to /opt/yay/unreal-engine/src/unreal-engine/Engine/Saved/BuildGraph/Make Installed Build Linux/Tag-Installed Build Linux Files.xml

BUILD SUCCESSFUL
AutomationTool executed for 4h 13m 10s
AutomationTool exiting with ExitCode=0 (Success)
==> Entering fakeroot environment...
==> Starting package()...
install: missing destination file operand after '/opt/yay/unreal-engine/pkg/unreal-engine/opt/unreal-engine/Engine'
Try 'install --help' for more information.
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: unreal-engine

Building the package like this:

$ yay --builddir /opt/yay unreal-engine

Any way to fix this manually, without having to compile everything again? Thanks.

Neko-san commented on 2022-11-16 10:17 (UTC) (edited on 2022-11-16 10:24 (UTC) by Neko-san)

The PKGBUILD and script edits the .desktop file dynamically to solve that, which should be done after a working package is installed (make sure you don't already have one in your ~/.local/share/applications folder)

As for those configure errors you mentioned, I'll take care of that today after I get some sleep; for now, just remove the bits in the PKGBUILD where those 3 are mentioned and it should be fine

juancarlospaco commented on 2022-11-16 10:02 (UTC) (edited on 2022-11-16 10:15 (UTC) by juancarlospaco)

Some errors from line https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=unreal-engine#n160

Unknown argument 'WithWin32'
Unknown argument 'WithLumin'
Unknown argument 'WithHTML5'

This line https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=unreal-engine#n194 complains install: missing destination file operand after 'unreal-engine/pkg/unreal-engine/opt/unreal-engine/Engine'.

I got no icon on my system, I think its because the icon and .desktop still says unreal engine 4?.

Neko-san commented on 2022-11-11 06:43 (UTC)

I'll implement this when I have a moment tomorrow; thanks for letting me know

I'll set this up for UE4 package as well, while I'm at it

juancarlospaco commented on 2022-11-10 22:10 (UTC) (edited on 2022-11-10 23:21 (UTC) by juancarlospaco)

This package needs to add the dependency openssl-1.1 and steam, for "Turnkey" thats like an internal program to detect Clang targets to compile to, otherwise it only compiles to Linux x86_64 or nothing, meaning you can not compile your game into a binary.

Steam needs to be added as dependency too, because it searchs for Steam SDK and .so binaries at startup in a broken symlink at $HOME/.steampath, error says Warning: Cannot determine whether '/home/juan/.steampath' is a directory - stat() failed with errno=2 (No such file or directory), the symlink also needs to be created.

It also needs to run these:

ln -s $HOME/.steampath $HOME/.steam/bin
mkdir -p $HOME/.config/Epic/UnrealEngine/5.0/Intermediate/
mkdir -p $HOME/.cnfig/Epic/UnrealEngine/5.0/Intermediate/
chmod +x /opt/unreal-engine/Engine/Binaries/ThirdParty/Mono/Linux/bin/xbuild
chmod +x /opt/unreal-engine/Engine/Binaries/ThirdParty/Mono/Linux/bin/mcs
mkdir -p /opt/unreal-engine/Engine/Binaries/Android/

You can try yourself what I am saying by running /opt/unreal-engine/Engine/Build/BatchFiles/RunUAT.sh Turnkey -utf8output -WaitForUATMutex -command=VerifySdk -ReportFilename="$HOME/.cnfig/Epic/UnrealEngine/5.0/Intermediate/TurnkeyReport_0.log" -log="$HOME/.config/Epic/UnrealEngine/5.0/Intermediate/TurnkeyLog_0.log" -platform=all and /opt/unreal-engine/Engine/Build/BatchFiles/Linux/Build.sh -Mode=QueryTargets -Output="/opt/unreal-engine/Engine/Intermediate/TargetInfo.json" -progress.

wilaze131 commented on 2022-11-03 09:56 (UTC) (edited on 2022-11-03 09:57 (UTC) by wilaze131)

@Neko-san I have /root and /home with separate partition.

so /home need 200-300 GB free space for compilation. (which i dont have this much free space left xD) and /root need 60+ GB free space for Installation directory (/opt/UE). right?

Can it actually being installed in /home partition tho like Unity Editor does?

Neko-san commented on 2022-11-03 07:37 (UTC)

@wilaze131

1) Compilation, in my experience, typically requires between 200 to 300GBs but the completed installation itself (not the package archive but the actual extracted data) is about ~57GBs or so

2) If you look inside the PKGBUILD file, you can configure where you want it to install, but it's set to install to /opt/unreal-engine by default

wilaze131 commented on 2022-11-03 07:17 (UTC)

Hi, how many space did i need to install this? and is it being installed on /home directory or /root directory?

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).