Package Details: ldtk 1.1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: ldtk
Description: Modern and efficient 2D level editor with a strong focus on user-friendliness
Upstream URL:
Keywords: 2D development gamedev
Licenses: MIT
Submitter: Zyper
Maintainer: Zyper
Last Packager: Zyper
Votes: 4
Popularity: 0.007576
First Submitted: 2021-02-16 23:02 (UTC)
Last Updated: 2022-04-16 13:48 (UTC)

Latest Comments

willianholtz commented on 2022-03-29 18:16 (UTC) (edited on 2022-03-29 19:06 (UTC) by willianholtz)

Actually what I find strange is that NPM takes the wrong link:

instead of:

I tried to edit the package but I couldn't find the line of this instruction

EDIT: Well I made the package based on appimage myself, just like that to work!

Zyper commented on 2022-03-29 18:03 (UTC)

@willianholtz Clearly there is something wrong with your connection to NPM servers. Are you using a proxy? Does npm work on your system and installs other things correctly? Does installing LDtk straight from the GitHub work? I don't think this problem is related to this AUR package, but if it is and there is something that needs to be changed in the PKGBUILD feel free to contact me here.

willianholtz commented on 2022-03-29 17:50 (UTC)


Still same error: request to failed, reason: connect EHOSTUNREACH 2606:4700::6810:1423:443

I have no more ideas of what to do. I searched for this error but I didn't find the solution

Zyper commented on 2022-03-29 16:01 (UTC)

Hey @willianholtz I checked a few days ago on two machines and had no problems with building. There was a problem with running though (which could be resolved by running ldtk as ldtk --in-process-gpu), which now seems to be fixed in v.1.0.0 and is working without problems.

willianholtz commented on 2022-03-29 15:43 (UTC)

First, thanks for the quick update!

Looking forward to getting home and installing this new update. I've been following for a while and I'm expecting a lot of improvements that deepnight was making.

By the way, were you able to fix the packaging errors that were happening in the previous build?

Zyper commented on 2022-02-15 09:22 (UTC) (edited on 2022-02-15 11:13 (UTC) by Zyper)

@justanotheruser2: The same thing happens to me when compiling from upstream (GitHub repo). I'm not an expert in Node.js either, but I'll try to investigate why that happens.

Edit: This is this issue: For now it can be resolved by hand when building from repo.

Edit2: There's also a problem with "GPU process isn't usable" error. Try running ldtk like this: ldtk --in-process-gpu

justanotheruser2 commented on 2022-02-15 08:35 (UTC)

Not sure if this is just me not understanding something basic (not used to javascript), but when running ldtk on fresh build I get:

(node:189057) UnhandledPromiseRejectionWarning: Error: Cannot find module 'fs/promises' Require stack: - /usr/share/ldtk/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js - /usr/share/ldtk/resources/app.asar/node_modules/electron-updater/out/main.js - /usr/share/ldtk/resources/app.asar/assets/main.js - at Module._resolveFilename (internal/modules/cjs/loader.js:961:15) at Function.o._resolveFilename (electron/js2c/browser_init.js:257:921) at Module._load (internal/modules/cjs/loader.js:844:27) at Function.Module._load (electron/js2c/asar.js:779:28) at Module.require (internal/modules/cjs/loader.js:1023:19) at require (internal/modules/cjs/helpers.js:77:18) at Object.<anonymous> (/usr/share/ldtk/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:8:20) at Module._compile (internal/modules/cjs/loader.js:1145:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1166:10) at Module.load (internal/modules/cjs/loader.js:981:32) (node:189057) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see (rejection id: 1) (node:189057) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [189057:0215/] GPU process isn't usable. Goodbye. zsh: trace trap (core dumped) ldtk

willianholtz commented on 2021-12-16 00:54 (UTC) (edited on 2021-12-16 00:54 (UTC) by willianholtz)

errr.. new error. [code] npm WARN using --force Recommended protections disabled. npm ERR! code EHOSTUNREACH npm ERR! syscall connect npm ERR! errno EHOSTUNREACH npm ERR! request to failed, reason: connect EHOSTUNREACH 2606:4700::6810:1123:443

npm ERR! A complete log of this run can be found in: npm ERR! /tmp/yaourt-tmp-willian/aur-ldtk/src/npm-cache/_logs/2021-12-16T00_32_44_486Z-debug.log ==> ERRO: Uma falha ocorreu em build(). Abortando... ==> ERRO: Makepkg não conseguiu compilar ldtk. ==> Reiniciar a compilação de ldtk ? [s/N] ==> -------------------------------------- [/code]

Zyper commented on 2021-12-12 19:05 (UTC)

@ColonelThirtyTwo: Done

ColonelThirtyTwo commented on 2021-12-08 17:37 (UTC)

Any chance you can add some desktop files? This doesn't show up in the Gnome apps list. Other than that, works well.

willianholtz commented on 2021-08-01 05:33 (UTC)

@Zyper thanx!! :)

hollunder commented on 2021-07-31 14:34 (UTC)

Works now, thanks for the timely fix Zyper.

I think this is not handled well by upstream. Would probably make sense for upstream releases to use tagged versions or something of the dependencies, otherwise issues like these are inevitable. As it stands every build will be different. Unless you specify some specific commit, like you have done here, but it will most likely still be different from the upstream 0.9.3 build.

Zyper commented on 2021-07-31 13:43 (UTC)

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.

hollunder commented on 2021-07-31 11:10 (UTC)

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.

willWallace77 commented on 2021-07-31 01:41 (UTC) (edited on 2021-07-31 01:43 (UTC) by willWallace77)

So I had a little trouble getting this one compiled today. During build I kept getting errors about Strings should be 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 --always

--cmd haxelib git heaps --always

--cmd haxelib git hxnodejs --always

--cmd haxelib git electron d438f04fbdbc8b798164bc01e3d27933c5baba48 --always

--cmd haxelib git heaps-aseprite --always

--cmd haxelib git ldtk-haxe-api 1ea2a42f71371d4c983bc922aa2b81b4209e8ced --always

--cmd haxelib git deepnightLibs 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.

willianholtz commented on 2021-07-08 01:44 (UTC)

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?

willianholtz commented on 2021-07-01 20:55 (UTC)

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

Zyper commented on 2021-07-01 19:47 (UTC)

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

willianholtz commented on 2021-07-01 18:05 (UTC)

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

Zyper commented on 2021-04-20 19:52 (UTC)

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

willianholtz commented on 2021-04-20 19:13 (UTC)

erro: file owned by 'LDtk' and 'ldtk': 'usr/bin/ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/AutoLayers_1_basic.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/AutoLayers_2_stamps.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/AutoLayers_3_Mosaic.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/AutoLayers_4_Advanced.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/Entities.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/SeparateLevelFiles.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/Test_file_for_API_showing_all_features.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/Typical_2D_platformer_example.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/Typical_TopDown_example.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/WorldMap_Free_layout.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/WorldMap_GridVania_layout.ldtk' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/Beach by deepnight.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/Cavernas_by_Adam_Saltsman.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/Inca_back2_by_Kronbits.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/Inca_front_by_Kronbits-extended.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/Monsters_and_Minions_by_Beowulf.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/RPG Graphics Icons by 7Soul's.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/SunnyLand_by_Ansimuz-extended.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/ldtk/samples/atlas/TopDown_by_deepnight.png' erro: file owned by 'LDtk' and 'ldtk': 'usr/share/licenses/ldtk/LICENSE'