Fix ARM compiler path on Windows

[parasyte]

Looks like the compiler path changed in recent versions. I'm using Version 12.3.Rel1, released July 28, 2023.

https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads

Possible fix for #44?

[parasyte]

Should this path really be hardcoded? Assuming the toolchain installer sets your path correctly, and it does in my case, this absolute path can just be removed, and the environment relied on. Doing this would be more robust since there will be no need to update crank in lockstep with the compiler toolchain.

I've confirmed this works for me:

diff --git a/src/main.rs b/src/main.rs
index 25359e2..c38e9be 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -28,8 +28,7 @@ const GCC_PATH_STR: &'static str = "/usr/local/bin/arm-none-eabi-gcc";
 #[cfg(all(unix, not(target_os = "macos")))]
 const GCC_PATH_STR: &'static str = "arm-none-eabi-gcc";
 #[cfg(windows)]
-const GCC_PATH_STR: &'static str =
-    r"C:\Program Files (x86)\Arm GNU Toolchain arm-none-eabi\12.3 rel1\bin\arm-none-eabi-gcc.exe";
+const GCC_PATH_STR: &'static str = "arm-none-eabi-gcc.exe";

 #[cfg(unix)]
 #[allow(unused)]

[boozook]

This looks like kinda breaking change for old versions and system without arm-gcc in the PATH. That's ok, but so need to bump minor version component.
Also as I see there's new problems with integration tests on CI.

[boozook]

Okay, that's ok, but I'm sure there also need to mention in the readme that arm-gcc should be in path on windows.

[boozook]

Also, how about use my new utils to find gcc? Here is example.

[parasyte]

WRT the new stuff, I'm going to have to migrate to it. When I started my project, none of that was even publicly available.

[parasyte]

Oh look, this fixes the broken Windows test, lol. 🎉

Yeah, I can update the readme.