tobil4sk
tobil4sk
Hi, it looks like this tool exists to solve issues like this: https://github.com/termux/termux-elf-cleaner?tab=readme-ov-file#termux-elf-cleaner. It claims to solve your error.
This seems to be the PR that fixes it in haxe 5: https://github.com/HaxeFoundation/haxe/pull/11168. Updating to haxe 5 solves the original error with `lime.app.Event` from my testing. Is there anything else...
> maybe the ! in the path may be an issue It could be that the `!` in your path is causing issues here: https://github.com/HaxeFoundation/hxcpp/blob/3f6de84d4decb0a7aa1131ebd527f623b1e2d2b1/toolchain/msvc-setup.bat#L14 You could double check to...
You could go to your hxcpp install, open the `toolchain/msvc-setup.bat` file and replace this line: https://github.com/HaxeFoundation/hxcpp/blob/3f6de84d4decb0a7aa1131ebd527f623b1e2d2b1/toolchain/msvc-setup.bat#L14 with: ``` @if exist "%InstallDir%\Common7\Tools\VsDevCmd.bat" ( ``` And see if that makes any difference.
Looks like the exclamation mark is the most likely explanation: https://ss64.com/nt/delayedexpansion.html > If DelayedExpansion is used in conjunction with a FOR command looping through a set of files, if any...
I ran the following commands in a local repo with lime installed (with no hxCodec install in the global repo). It compiled without any issues: ``` haxelib git hxCodec https://github.com/polybiusproxy/hxCodec...
> Now not only cwd but also resolution of path to haxelib repo is impacted, as it's resolved from that cwd instead of "real" cwd. As mentioned in #272, the...
I think this is the line that's causing the issue: https://github.com/HaxeFoundation/hxcpp/blob/b1359b43354aa52e7da29dbdd711bace63a51685/tools/hxcpp/PathManager.hx#L109 It changes the cwd to `HAXEPATH` before executing the `haxelib path` command. So that would make sense how setting...
@sphis-sinco This thread was specifically about a bug with hxcpp resolving library paths, and it has been resolved. Please open a new issue with your exact problem, a minimal sample...
I've looked into it a bit more and it seems the error message is still coming from hxcpp, so I'm reopening. Please still provide your command outputs.