|
|
|
|
@ -75,7 +75,7 @@ $newPath = $env:PATH + ";$winlibsPath\mingw64\bin" |
|
|
|
|
|
|
|
|
|
Yes, this is all you need to do, but Microsoft employees weirdly won't put certain competing |
|
|
|
|
products in the PATH in order to add friction to the install so that people just give up and use |
|
|
|
|
their commercial products. As I said, this is about the stupidest most banal things ever, and we'll |
|
|
|
|
their commercial products. As I said, this is about the stupidest most banal thing ever, and we'll |
|
|
|
|
fix it with an equally stupid and banal PowerShell script: |
|
|
|
|
|
|
|
|
|
```shell |
|
|
|
|
|
