translatenix

@bioball Ready from my side. See latest commit message for details. Quite happy with the cleanup.

> We have an existing pattern of having unconfigured() and preconfigured() builders; see EvaluatorBuilder, ConfigEvaluatorBuilder, ValueMapperBuilder, etc. I think let's follow that. According to the Javadoc, `Executor` "evaluates Pkl modules...

> I don't see any issues with the set of options provided by preconfigured(). This is an opt-in behavior, and users are expected to know what preconfigured() means. It's actually...

I've made 2 out of 3 requested changes and have squashed my commits. I'll leave any builder changes to you. I've also rebased my Gradle 8.6 PR, which I'd love...

A great first step would be to fix the Git clone issues. They block all other work/contributions.

Thanks for the pointers! I found more info here: https://www.graalvm.org/latest/reference-manual/native-image/guides/build-static-executables/#prerequisites-and-preparation I think most (WSL) Linux users won't bother to set up a musl toolchain. But we'd still like to run...

Sent https://github.com/apple/pkl/pull/83 for the musl toolchain check. I'll leave it to you to clarify the "setup Gradle" instructions because I don't know if/what setup you'd like to recommend. All I...

This PR achieves exactly what you're proposing: If no musl toolchain is installed, `buildNative` should only build `linuxExecutableAmd64` and should skip `alpineExecutableAmd64`. The problem isn't specific to WSL but applies...

Is there a timeline to fix this? Developing on WSL is really painful. Gradle and esp. IntelliJ are extremely slow (30s pause is normal), and important IntelliJ features such as...

@bioball Windows support is very important to me. I'd be willing to work on this first step, but I'd need some guidance wrt. changing the cache file layout.