A lot of this confused my since I hate (am not friends with (never got to know)) external tools outside of compiling. Wjy can't it just be Files -> Compiler => Product, instead of all this extra vomplex BS??
Though, thanks for the advice, I'll try to look in to it further, and see if I can learn anything.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What people usually do is to setup CI/CD pipeline that automatically builds the project for each target when a new release is made.
For example, you can see in the assets section of this project, the different binaries that target different platforms.
However, you could always write a script to do this step locally. Take a look at rust-lang.github.io/rustup/cross-c...
I believe having a seperate binary for each platform, will lead to smaller and faster binaries.
A lot of this confused my since I hate (am not friends with (never got to know)) external tools outside of compiling. Wjy can't it just be Files -> Compiler => Product, instead of all this extra vomplex BS??
Though, thanks for the advice, I'll try to look in to it further, and see if I can learn anything.