Disclaimer: Not legal advice, ask your lawyer!!
If you use #Rust in a corporate environment you should be aware of the licensing that exist on #Windows. #RustLang uses Visual Studio Build tools, and it follows the rules of VS Community edition unless you have a payed license.
250 pc's or $1 mill revenue will put you squarely into #Microsoft definition of enterprise.
The community license is here: https://visualstudio.microsoft.com/license-terms/vs2022-ga-community/
The post that reminded me of this is: https://internals.rust-lang.org/t/use-lld-by-default-on-windows-to-mitigate-microsoft-c-build-tools-licencing-issues/16606
Why would one not just use the x86_64-pc-windows-gnu target (MinGW) instead? Are there any downsides?
@guenther @trevorfsmith not sure, depends on the license I guess. I have used it to cross-compile windows binaries on Linux systems in the past, and they did run on Windows. That was C and not rust though.
For a corporation the license fee should be ok though, but it does seem like it is undercommunicated that it might be required.
chaos.social – a Fediverse instance for & by the Chaos community