translatenix
translatenix
I'm trying to build Pkl on Ubuntu 22.04/WSL 2.0.14. (I'd prefer to build directly in Windows but ran into https://github.com/apple/pkl/issues/20 and failing tests.) After reading through `DEVELOPMENT.adoc`, I have the...
This improves the development experience for (WSL) Linux users. They can now run "./gradlew buildNative" without having a musl toolchain installed. In this case, only the dynamically linked executable will...
This is the first step in #20 and critical to unlock outside contributions.
- remove "Setup Gradle on your system" (too vague and doesn't seem necessary) - remove "gw pkldoc" (obsolete) - improve docs for common build commands
This allows to "Run all Tests" in IntelliJ without getting lots of test errors because "pkl-alpine-linux-amd64" etc. doesn't exist.
Moving to `java.net.http.HttpClient` brings many benefits, including: * HTTP/2 support * optional async mode * no need to set a system-wide default `SSLSocketFactory` Instead of directly interfacing with `java.net.http.HttpClient`, I'd...
When an external contributor submits a PR, CI builds are on hold until manually authorized by a team member. This complicates external contributions as we won't know the build outcome...
It would be very helpful to know when we can expect new releases (with our contributions!) and what the high-level roadmap is (e.g., Windows support).
CliDownloadPackageCommand -> CliPackageDownloader (consistent with CliProjectPackager/CliProjectResolver) CliAbstractProjectCommand -> CliProjectCommand (consistent with CliCommand) As I learned yesterday, I'm touching a public API here. Let me know if this is acceptable.
When I open the Gradle project in IntelliJ, pkl-core/generated/truffle isn’t marked as generated sources dir. As a result, I’m getting hundreds of “unresolved symbol” errors in Java source files. Is...