3 ms·

Nice intro. I had to go through this yesterday on a cloud instance and hadn’t used windows in awhile. Instead of using this install GUI I first installed choc

Nice intro. I had to go through this yesterday on a cloud instance and hadn’t used windows in awhile. Instead of using this install GUI I first installed chocolatey. Once that was ready from powershell it’s a quick ‘choco install git’. Getting visual studio build tools wasn’t as easy (was compiling rust/c++ so had it as a dependency). I managed to avoid Internet explorer entirely by ‘choco install Firefox’ and then managed to go through the painful web workflow VS community edition download. I really wonder how I managed on Windows for so long in my former career. It’s night and day vs Linux or Mac.

michaelsbradley 5y ago
With MSYS2 installed on your Windows cloud instance, in a Bash shell for e.g. its UCRT64 environment, you could use pacman to get your dev setup in place: pacman -S base-devel git mingw-w64-ucrt-x86_64-toolchain mingw-w64-ucrt-x86_64-rust Other build tools like cmake, etc. are also readily available via pacman. I've found this approach helps make developing on Windows a lot more like I want, i.e. more like my experiences on Linux and macOS. Whether the "-toolchain" package in the install-list above (gcc and friends) is suitable for your needs, I'm not sure, though note that the "-rust" package brings in llvm automatically, so your bases are probably covered unless you have a strict requirement to use Microsoft's toolchain.
easton 5y ago
winget is built into Windows 10 and 11 and works as well as chocolatey (in 90% of cases, still some apps missing). winget install -s winget git ; winget install -s winget firefox ; winget install -s winget vs2022-buildtools --interactive will get you what you listed. the "-s winget" option bypasses the Microsoft Store source, but you can permanently remove that with "winget source remove msstore". if you want to browse for more apps (and generate commands to install them) you can with https://winstall.app https://winstall.app.
brnt 5y ago
I co-maintain a piece of software and I would love to have a Windows binary. We have few dependencies, all well behaved and we dont use any OS APIs. It's a Cmake projectand I'm sure if I would get it to compile on Windows it would work fine. I gave it a shot twice, first by hand, second time through Github CI. I just don't get how any of this works on Windows.

michaelsbradley 5y ago

With MSYS2 installed on your Windows cloud instance, in a Bash shell for e.g. its UCRT64 environment, you could use pacman to get your dev setup in place: pacman -S base-devel git mingw-w64-ucrt-x86_64-toolchain mingw-w64-ucrt-x86_64-rust Other build tools like cmake, etc. are also readily available via pacman. I've found this approach helps make developing on Windows a lot more like I want, i.e. more like my experiences on Linux and macOS. Whether the "-toolchain" package in the install-list above (gcc and friends) is suitable for your needs, I'm not sure, though note that the "-rust" package brings in llvm automatically, so your bases are probably covered unless you have a strict requirement to use Microsoft's toolchain.

easton 5y ago

winget is built into Windows 10 and 11 and works as well as chocolatey (in 90% of cases, still some apps missing). winget install -s winget git ; winget install -s winget firefox ; winget install -s winget vs2022-buildtools --interactive will get you what you listed. the "-s winget" option bypasses the Microsoft Store source, but you can permanently remove that with "winget source remove msstore". if you want to browse for more apps (and generate commands to install them) you can with https://winstall.app https://winstall.app.

brnt 5y ago

I co-maintain a piece of software and I would love to have a Windows binary. We have few dependencies, all well behaved and we dont use any OS APIs. It's a Cmake projectand I'm sure if I would get it to compile on Windows it would work fine. I gave it a shot twice, first by hand, second time through Github CI. I just don't get how any of this works on Windows.