Chase Whitener

> CPython has supported `Program Files` since forever. You install packages into the Program Files site as admin (eg `C:\Program Files\Python312\Lib\site-packages`) or into your user folder (eg `%APPDATA%\Python\Python312\site-packages`). > >...

That `mingw32-make.exe` comes directly from [WinLibs](https://winlibs.com/). https://github.com/brechtsanders/winlibs_mingw

We put copies in place here: https://github.com/StrawberryPerl/spbuild/blob/main/5.34/Dockerfile#L30-L31 to help with builds

https://github.com/gwenshap/DBD-Oracle/blob/dc6325d4f96da3c54fc6862512f4de67e5ec03e2/README.win64.txt#L7 seems to indicate we can use either of the instant clients, so I'd say basic. I don't know if we need any of the features excluded from basic for...

I get the desire for major version completeness, but I'm also "meh" on this one. We're currently at 5.40, so I don't see much need in a 5.34 realistically.

This is not an issue, but a requirement for Perl on Windows. In the unfortunate event that you have an alternate MinGW installed, you will have to be careful about...

You can yank the C compiler out of your own `PATH` unless you're installing things if that's your preference. However, some FFI modules and others will misbehave if there's no...

It matters what version of MinGW the version of Strawberry you're using was _built_ with. Many of them around that are installable on your version of Windows. They're not all...

Unfortunately, we can't account for every non-vanilla machine build out there. We need these paths in the environment to allow Perl to function as expected. Knowing how the install works...

The problem is that for Windows, MinGW _is_ a core part of Perl and it has to be the same version of MinGW that Perl was built with. There is...