Saleem Abdulrasool
Saleem Abdulrasool
> OK, makes sense, but what is your plan here? When I suggested a similar organization last year, it was rejected. We shouldn't special-case only the Android SDK on Windows...
I believe that the currently marked Swift issues are dealt with except for the bridging header disagreement. That might be something that can get addressed in the next cycle depending...
Do they reproduce on Windows or require a macOS host?
Unfortunately, the only host that I currently have with a development toolchain setup is Windows.
It might be related to that PR - I have a follow up that I am working on right now. This sounds like there is an issue with the DLLs...
I think that https://github.com/swiftlang/swift/pull/80157 might fix the issue. Longer term, we need to figure out how to do some smoke testing for Windows with the toolchain itself.
@bkhouri that doesn't make sense - I just installed that locally in a Windows Sandbox: ``` C:\Users\WDAGUtilityAccount>swiftc -v Swift version 6.2-dev (LLVM 3c4a54b02dd62b7, Swift a40a7be6945a895) Target: x86_64-unknown-windows-msvc ``` ``` C:\Users\WDAGUtilityAccount>swift...
Well, I think that we don't want to put more stuff in the resource directory - we should be putting less there. But the layout itself of the SDK, we...
> > Well, I think that we don't want to put more stuff in the resource directory - we should be putting less there. > > This has nothing to...
Yes, these changes, while generic, are meant for Windows. The default is to continue to use the existing layout, but you can opt-in via `-D ....` to install into the...