winget makes first build a lot more complicated

[Pumbakos]

I just started using Windows after 2 year break and I am new to rust ecosystem, I was using macOS (where I could use brew for those who don't know) so I started using winget as documentation states.
I've encountered an issue where avr-gcc could not interpret --print-memory-usage flag. At first glance, I did not suspect versioning because "Hey, I just installed it".
The error was error: linking with ‘avr-gcc’, so I started poking around using some rustflags and various linkers because that's what some of the stackoverflows answers have said. Then I realized that winget installed winavr-20100110 that seems to be quite old. I followed this great article by Tony Mitchell and turned out to be working.

This is the line that caused all that (link to README.md):

winget install AVRDudes.AVRDUDE ZakKemble.avr-gcc

[stappersg]

On Sun, Oct 20, 2024 at 12:37:11PM -0700, Dawid Pałubiak wrote: using Windows This is the line that caused all that ```shell winget install AVRDudes.AVRDUDE ZakKemble.avr-gcc ```

patches welcome. Slightly longer version: Acknowlegde on "It does not work on my platform". Do not expect that "works on **all platforms**" is a top priority. Please update yourself the README.md with how to install winget. (A link to "How to install winget on Microsoft Windows 11" will do.) Groeten Geert Stappers -- Silence is hard to parse

[Rahix]

Agreed. I don't have a Windows system to check with so I rely on feedback from users on what works. If the current instructions have problems, please send a PR to update/fix them :)