...from a C programmer.
I have a small side-project which appears to be a good candidate to let me get familiar with Rust. However, schedule is tight and I can't change my programming environment; if I can "shoehorn" Rust compiling and building into my existing "workshop" I can do it, if not I'll have to wait for another opportunity.
All my source code lives in a directory that is read/write only when the code is being editing, when it is compiled, linked and tested it is read-only. Can rust compiler and linker operate in such environment?
In this instance any "version control" automatism is an unwelcome complication. Can I completely by-pass the necessity to deal with it in Rust/Cargo?
While I can do what is necessary to copy required components from the Internet to set up the development environment, while coding and testing I am on a local network only,, without Internet access on the development machine. Is this likely to present a problem?
For a simple statically linked command-line Linux executable, are there any Rust-related run-time files required to be passed on to the user of the program?