| 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 |
| Last Packager: | Neko-san |
| Votes: | 76 |
| Popularity: | 0.052791 |
| First Submitted: | 2016-05-01 18:37 (UTC) |
| Last Updated: | 2024-11-16 03:10 (UTC) |
@anthillsocial If you don't have dotnet installed, let me know; it might be that a dependency is missing and Unreal just isn't telling us. Normally, I'd run namcap on a completed archive to find out but namcap doesn't handle large packages like Unreal too well (throws errors)
If you do have dotnet installed, try setting "arch_auto" in the PKGBUILD to false; I didn't have an issue with it, but I'd like to know if this is a possible cause for your problem
I'm getting the "Running AutomationTool..." and "Setting up bundled DotNet SDK" build message errors:
MSBUILD : error MSB4166: Child node "2" exited prematurely. Shutting down.
RunUAT ERROR: AutomationTool failed to compile.
==> ERROR: A failure occurred in build().
Aborting...
:: Unable to build unreal-engine - makepkg exited with code: 4
Any tips?
@greenhandzdl I tried running makepkg in the build directory, and it looks like the PKGBUILD uses 5.2-release rather than 5.2 as the branch to retrieve from. Modifying the PKGBUILD locally to use 5.2 should work.
Took 7596.348587500001s to run dotnet, ExitCode=6
UnrealBuildTool failed. See log for more details. (/home/greenhandzdl/Library/Logs/Unreal Engine/LocalBuildLogs/UBT-UnrealEditor-Linux-DebugGame.txt)
AutomationTool executed for 2h 9m 38s
AutomationTool exiting with ExitCode=6 (6)
RunUAT ERROR: AutomationTool was unable to run successfully. Exited with code: 6
==> ERROR: A failure occurred in build().
Aborting...
-> error making: unreal-engine-exit status 4
-> Failed to install the following packages. Manual intervention is required:
unreal-engine - exit status 4
Running /opt/unreal-engine/Engine/Build/BatchFiles/Linux/Build.sh -projectfiles -project="/home/alberto/Repositories/UnrealEngine/Learning/Learning.uproject" -game -engine -progress Setting up bundled DotNet SDK chmod: changing permissions of '/opt/unreal-engine/Engine/Build/BatchFiles/Linux/../../../Binaries/ThirdParty/DotNet/6.0.302/linux/dotnet': Operation not permitted"
This error still happens with the pinned commands.
Edit: Fixed by moving unreal to nonroot directory.
Fixed; I had forgot to update the checksum for the script for some reason
The file unreal-engine-5.sh fails its validation check. The package can no longer be built.
Validating source files with sha256sums...
unreal-engine-5.sh ... FAILED
@juancarlospaco No, that's outside the scope of the PKGBUILD.
If you're using KDE Plasma, thia can be easily done in the system File Association settings.
In other desktop environments, how you do this may vary, and is outside of my control. It's up to you, as the user, to figure that out.
Ideally, UE5 should update this itself but it doesn't because Epic doesn't prioritize Linux.
If you do figure out an agnostic way to do this thay doesn't require root, let me know and I'll implement it, but otherwise it is not a goal of this package to set up.
Is possible to add to the PKGBUILD to open *.uproject with Unreal Engine by default after install?,
currently it opens with the plain-text editor and thats useless. Thanks.
@nic-hartley The reason why that folder path doesn't exist is because the build failed, as you mentioned:
Unhandled exception: One or more errors occurred. (The type initializer for 'UnrealBuildBase.Unreal' threw an exception.)
I can't give you an exact reason for why this happened, because it shouldn't have, but all I can advise is that you just nuke the whole thing and start over.
I'm going to implement an error detection in the build function of the PKGBUILD to stop makepkg before it reaches the package function; so, you shouldn't see stuff like folders not existing messages if the build itself fails anymore.
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
777permissions. 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.