Saleem Abdulrasool

This causes a breakage locally for me due to the modulemaps now not being found.

Yes, on Windows, with an Android SDK being used to build; I'll try to get this soon, I have a different state now to fix a few issues with swift-foundation...

Okay, rebuilt with this change and got the error logs from what previously would build fine: ``` S:\Applications\Android\ndk\r26d\toolchains\llvm\prebuilt\windows-x86_64\sysroot/usr/include\jni.h:27:10: note: while building module 'std' imported from S:\Applications\Android\ndk\r26d\toolchains\llvm\prebuilt\windows-x86_64\sysroot/usr/include\jni.h:27: 25 | 26 |...

IIRC, it was simply using the Android SDK on Windows and cross-compiling [swift-firebase](https://github.com/thebrowsercompany/swift-firebase) for Android. There has been a series of regressions in the toolchain which is currently occupying my...

@egorzhdan unfortunately, that is the version of the libc++ that is shipped in the latest Android SDK so we cannot update that. @finagolfin I strongly disagree with that - this...

I am willing to do that, but am currently dealing with a number of recent regressions in the build and trying to finish some of the changes for 6.0 regarding...

I'd say that a follow up change is better - that allows us to get this change in (possibly cherry-picked to release) while we fix the option naming and test...

There are small UI differences IIRC between the two path. `mt` should be called on the binary, especially for modern Windows applications. The problem is that the SPM tooling doesn't...

> it would suggest that the compiler is actually capable of producing valid object files in these formats, but that's almost certainly not true until someone actively builds that support....

@finagolfin we only have a single directory there because it takes time to build. The installer will have all the architectures under the same directory, just like Windows already does...