#RustLang "cargo" Build Script can call GCC to compile C code ... Maybe we use this instead of "make" to build #BL602 IoT SDK on Windows? 🤔
https://doc.rust-lang.org/cargo/reference/build-script-examples.html
@lupyuen
My guess is it wont change much. Maube even go sluggtly worse.
@lupyuen
If you have to stick with makefiles and gcc just make sure you run gcc and make from cmd. Its best you can get so far.
@lupyuen
Btw good news from natanz.
https://twitter.com/IsraeliPM/status/1381305491784134656?s=20
@lupyuen
One cost is wsl one is msys bash one major is launching thousands of pricesses which are inefficient.
@lupyuen use the https://lib.rs/cc crate for this. It ensures Rust's compilation settings are copied to the C compiler, and it finds the right compiler for cross compilation, weird platforms etc.
@lupyuen
Try clang plus cmd
I might try to prebuild clang for you for win. Clang is generally faster in compile times over gcc due to diff arch. Less exes less processes etc. Integrated assembler and linker etc.
Sidenote try to set up linux build machine. 100s of processes there is no prob.
another thing to try out distributed and or incremental builds.
Dumping the #BL602 GCC Commands from "make" ... And running them under Windows CMD ... So much faster!
🤔