Plugin doesn't respect `CARGO_HOME` environment variable

[cyruspyre]

Currently, the plugin looks for cargo executable using a hardcoded path, which fails for users who have a custom installation path specified via the CARGO_HOME environment variable.
I believe the fix is trivial and just involves resolving cargo using CARGO_HOME or falling back to hardcoded path if CARGO_HOME doesn't exist.

Relevant line:

https://github.com/andrefigas/RustJNI/blob/36ec8def4fd18db42c13f2d404e565227826cbd7/gradle-plugin/src/main/kotlin/io/github/andrefigas/rustjni/RustJNI.kt#L77

[devandrefigueiredo]

You're right. Relying on a hardcoded path makes the plugin less flexible and can cause issues in custom environments.

I'll work on an improvement that allows the path to the cargo executable to be customised via local.properties

Tks for your feedback

[devandrefigueiredo]

Hello, could you try it again with version 0.0.26?

[cyruspyre]

Thank you. With v0.0.26, it looks like the plugin forgets to append .exe file extension when searching for executables on Windows. So, it throws an error stating that the expected Rust executable wasn't found in the directory, even though it exists. This probably doesn't affect Linux or macOS systems.

[devandrefigueiredo]

You're right. Thanks for your feedback!
I just created a PR to fix that regression.

Currently, our CI runs on a Linux machine only, so this might be a good reminder for us to consider validating it on other operating systems as well.

[devandrefigueiredo]

You're right, thanks for your feedback.
I just created a PR solving that regression.
Curtrently, our CI run over a linux machine, maybe it is a flag for we think about to validate it over the other SOs

[devandrefigueiredo]

Regression fixed 0.0.27
Could you test it again pls ?

[cyruspyre]

The issue has been fixed, thank you.