tobil4sk

> Is there a reason that both pcre1 and pcre2 are involved in the build process? `pcre1` is used by the eval target for regex in the standard library, which...

According to this comment left on the commit, pcre should be downloaded from homebrew (to avoid the hassle of having to build manually): https://github.com/HaxeFoundation/haxe/commit/62ee6a9a8e727de30ac7c8f6c82a3e8f42b9a22b#r73655101 > it's instead getting pcre1 from......

Also, I think we can probably just not build pcre2 for now, and see if anything breaks because of it (and if it does, we should probably just use homebrew...

Can't we get homebrew to build from source? That way we ourselves don't have to worry about our commands for installation breaking in the future, as some will probably fix...

It seems homebrew should build from source automatically if no bottle is found for the current system: https://docs.brew.sh/FAQ#why-do-you-compile-everything However, you're right about the xcode requirements. It will end up being...

> Right, but a bottle will almost always be available for us, since homebrew tends to support the last 3 versions of macOS. Ah right I see, that makes sense....

> It seems to me prerequisite dependencies for the Lua target could conceivably run before Haxe itself is built. The build environment is separate from the test environment, and is...

Yes, the error still comes up, for example in the latest run: https://github.com/HaxeFoundation/haxe/runs/6769262225?check_suite_focus=true#step:11:27

Compared to Neko and Hashlink, migrating eval to pcre2 is a bit more involved. The current ocaml pcre library used by haxe is just a copy of: https://github.com/mmottl/pcre-ocaml (besides minor...

If the constructor route isn't possible, I think something like `createFilled()` would make the purpose more explicit.