tobil4sk
tobil4sk
What about adding a flag like `HXCPP_COLOR`, and then the scripts that install haxe in these ci environments can just make sure that is set?
If we are intending to support older ndks for now (see #1925), then it may make sense to leave in armv5
This may be related to https://github.com/HaxeFoundation/neko/issues/281, since both started happening when the threads were added in #585.
I've also been able to reproduce this with hashlink (and previously with hxcpp too). This makes sense as their code is quite similar. It seems that when attempting to create...
This happens because of the following situation: 1) Process stdin handle A closed at p.stdin.close(), releasing handle A 2) Lock 1 (for git invocation 1) receives handle A 3) Process...
> One does not build from source independent of the package management system, one leverages the package management system to build from source. The instructions in the README are intended...
ab378107e8cde6f61d9b9b9ef1042dd31b7b5e0d was included in the 2.4.1 release, closing
> Actually im reopening this because now i cant compile with 8.1.2 and below Lime 8.1 did not support arm64 so this is expected, you need to use 8.2 for...
We mainly need `PLATFORM_NUMBER` for hxcpp 4.3.2, where it became configurable however min sdk 21 wasn't set by default yet for 32 bit architectures. This may actually be useful to...
> We mainly need PLATFORM_NUMBER for hxcpp 4.3.2 It turns out I had confused myself, 4.3.2 does not include the change so `PLATFORM_NUMBER` does nothing unless using git hxcpp, where...