Arch Linux User Repository

Upstream build system uses always up-to-date versions of external dependencies and they became out-of-sync with LDtk 0.9.3 code base. Based on @willWallace77 suggestion I specified commit hashes for each Haxelib. I've made it for all of the libs and used commits from around Apr 23.

@hollunder: I've tested it now on two machines so it should work. I've run into the same NodeTools.hx:100: lines 100-102 : Too many arguments error one time, but removing .cache/<aur-tool> (for yay: .cache/yay) solved it.

@willWallace77: Thanks for letting me know about the issue. Also I don't think chmod 755 for /usr/share/ldtk/chrome-sandbox should be necessary, because it's already installed with those permissions (line 45 in PKGBUILD).

@willianholtz: Those changes also fix the issue we were having with settings not being saved.

For me it still breaks after your fixes Will: ldtk/src/.haxelib/deepnightLibs/git/src/dn/js/NodeTools.hx:100: lines 100-102 : Too many argumentsldtk/src/.haxelib/deepnightLibs/git/src/dn/js/NodeTools.hx:100: lines 100-102 : Too many arguments

Either broken packaging or broken build system. I'm not familiar with Haxe build stuff.

So I had a little trouble getting this one compiled today. During build I kept getting errors about Strings should be ld.data.localeString. There is an ongoing issue on the git repo about string locale so I think this might be it. I'm not sure if it can be pushed to later version but I got it to work changing the commit pulls in setup.hxml

Setup.hxml I used:

--cmd haxelib git castle https://github.com/deepnight/castle --always

--next
--cmd haxelib git heaps https://github.com/deepnight/heaps.git --always

--next
--cmd haxelib git hxnodejs https://github.com/HaxeFoundation/hxnodejs.git --always

--next
--cmd haxelib git electron https://github.com/tong/hxelectron.git d438f04fbdbc8b798164bc01e3d27933c5baba48 --always

--next
--cmd haxelib git heaps-aseprite https://github.com/AustinEast/heaps-aseprite.git --always

--next
--cmd haxelib git ldtk-haxe-api https://github.com/deepnight/ldtk-haxe-api.git 1ea2a42f71371d4c983bc922aa2b81b4209e8ced --always

--next
--cmd haxelib git deepnightLibs https://github.com/deepnight/deepnightLibs.git b81e20f84f86c4fa44552161e0eeadea2c9c5cb1 --always

I also ran into an issue with /usr/share/ldtk/chrome-sandbox needing to be mode 4755 Adding a chmod to PKGBUILD sorted that.

Hello again! I managed to solve my problem, did the normal installation through its package, and then downloaded the appimage version from github, moved to /usr/share/ldtk. I gave chmod +x permission and that's it! I put the correct shortcuts and it worked!

Isn't it an idea to make a new package by getting the appimage file directly?

@Zyper I thought about talking to deepnight, but decided to post here first. I ran the package via appimage, in my user's folder and it worked, it saves the settings, but this way, it's not the right one to use.

@willianholtz I'm having the same issue on new package installation. Thanks for pointing that out! I see that settings.cfg file is created and the settings are saved, but for some reason LDtk cannot load it. It was working before for this version of AUR package, so I suspect something changed in LDtk's external lib which is downloaded from git during package installation. I will contact the author on GitHub.

@Zyper The Package after compiled is not saving the settings. I have a newly installed Arch machine.Is it something from ldTK? or some permission from the arch itself.

ps: My user is in the correct groups.

@willianholtz My guess is that ldtk AUR package probably collides with non-AUR LDtk package installed from different source. You can only have one of them installed, so uninstall the other.