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: 0.44
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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 82 Next › Last »

kerm commented on 2022-11-22 04:55 (UTC)

Hmm another error...

mv: cannot stat '/home/joshua/.cache/yay/unreal-engine/src/unreal-engine//home/joshua/.cache/yay/unreal-engine/src/unreal-engine/*': No such file or directory

This is becoming quite tedious, is their a way that the built files can be cached... having to re-run the update completely takes hours only to error again

coolitic commented on 2022-11-22 03:09 (UTC)

I am doubtful that there is something wrong w/ my system-configuration regarding that, considering that I have installed other packages in the same aur folder on my external drive that utilize the $pkgdir variable, and they don't seem to have any strange folder layouts under the pkg folder.

But I guess I'll have to look for solutions on my own, all things considered.

Neko-san commented on 2022-11-22 01:48 (UTC) (edited on 2022-11-22 01:49 (UTC) by Neko-san)

No, it doesn't. ${_install_dir} is a relative path and I only ever call it when touching things inside of ${pkgdir} for packaging; now, ${pkgdir} IS an absolute path, but I don't define that, makepkg does.

That being said, the only way that can go wrong is if your system somehow misinterprets what ${pkgdir} means. That's completely out of my hands.

Additionally, you might have your drive mounted via your desktop environment instead of /etc/fstab; in which case, I advise you mount with fstab instead to minimize other potential interferences on your system. That said, I'm not responsible for the reason why.

coolitic commented on 2022-11-22 00:31 (UTC) (edited on 2022-11-22 00:54 (UTC) by coolitic)

I have not only rebooted my system plenty of times, I've also run this script from a fresh-clone. If it helps at all, that path is for my external drive, which shouldn't have any problems as I store all my AUR packages on an external drive.

I'm not well-versed in creating AUR packages, but is it possible that ${_install_dir} is utilizing an absolute path?

Neko-san commented on 2022-11-22 00:28 (UTC)

Then point out where in the script and prove it, because I've been over this thing over 17 times

coolitic commented on 2022-11-22 00:26 (UTC)

That path is simply the absolute path, since my package is in /run/media/username/SE800/sources/aur/unreal-engine/. Meaning somewhere in the script, an absolute path is being used, which is obviously incorrect.

Neko-san commented on 2022-11-22 00:08 (UTC) (edited on 2022-11-22 00:08 (UTC) by Neko-san)

I've made changes to it now to use more explicit paths and to use find to look xbuild and mcs now

As for this: /run/media/username/SE800/sources/aur/unreal-engine/pkg/unreal-engine/opt/unreal-engine/run/media/username/SE800/sources/aur/unreal-engine/src/unreal-engine/

This path isn't represented in the bash code at all; I advise that you reboot your system

coolitic commented on 2022-11-21 23:36 (UTC) (edited on 2022-11-21 23:46 (UTC) by coolitic)

Similar thing happened: chmod: cannot access '/run/media/username/SE800/sources/aur/unreal-engine/pkg/unreal-engine/opt/unreal-engine/Engine/Binaries/ThirdParty/Mono/Linux/bin/xbuild': No such file or directory

And again, this is a folder path that should not exist and is where all the files are going: /run/media/username/SE800/sources/aur/unreal-engine/pkg/unreal-engine/opt/unreal-engine/run/media/username/SE800/sources/aur/unreal-engine/src/unreal-engine/

Paths are being set incorrectly somewhere. Also, next to the run folder under pkg/unreal-engine/opt/unreal-engine/ is an Engine folder, if that helps.

coolitic commented on 2022-11-21 17:17 (UTC) (edited on 2022-11-21 17:18 (UTC) by coolitic)

One thing that's annoying is that if something fails in package() and you run makepkg again, you have to rebuild everything from scratch (one could just move files back manually, but that's not ideal). Perhaps it would be a good idea to have moving the build files as the last thing that package() does? That way, if anything else fails, we won't lose precious build files and have to recompile.

Neko-san commented on 2022-11-21 08:42 (UTC)

Fixed

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 82 Next › Last »