Closed saulecabrera closed 3 weeks ago
Testing
The best way to test this change at this time is to download the Windows executable available in my fork and make sure that it runs correctly e.g. javy --version
.
I considered adding a CI step, but unfortunately there are several considerations:
Description of the change
Javy version 1.4.0 statically linked to the C runtime. Such version was built with Rust 1.75.
Javy version 2.0.0, built with Rust 1.79.0, which doesn't perform static linking by default. This commit adds a directive to preserve the same behavior as in v 1.4.0.
Checklist
javy-cli
andjavy-core
do not require updating CHANGELOG files.