-
Notifications
You must be signed in to change notification settings - Fork 43
WiX: remove extraneous architecture in search path #120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Adjust the location of the swift modules to overlap across SDKs. The directory form of the swift module can easily overlap and co-exist. Now that the driver has learnt to scan the non-architecture dependent location in addition to the architecture location dependent path, we can unify the swiftmodule content in the SDK to a simpler layout. The layout now is: ~~~ SDKROOT `- usr `- lib `- swift `- [platform] +- [module].swiftmodule | `- [triple].{swiftdoc,swiftmodule,swiftinterface} `- [arch] `- [import library] ~~~ On Windows, it would be preferable to further remove the intermediate platform as we have that information earlier in the path. Subsequent work remains to now ensure that the package manager will similarly allow the XCTest swift modules to collapse. While in theory it is possible to create a multi-architecture import library, it is valuable to support user-selectable SDK installation which requires that the we create the import libraries on the fly for the selected architectures. It is more convenient from a distribution perspective to simply make the content static and as such continue to use the architect dependent directory for the import library unlike the swift module. This is dependent on swiftlang/swift#42419.
@compnerd is this ready to be merged? |
Yes, I believe it is; I really wish that we could kick off toolchain builds that we could easily test with the changes. |
You can using the cross PR testing |
Hmm, it seems that it still doesn't report the generated installer - is there a way to get that to test? |
You should be able to download it now. I started a build over the weekend. |
Bleh, seems to be missing a change in swift-driver; thanks for setting up the download! |
Just verified, this is ready to go. Thanks for the ping on this @shahmishal! This is actually going to help make the 5.7 release for Windows even better :) |
Adjust the location of the swift modules to overlap across SDKs. The
directory form of the swift module can easily overlap and co-exist. Now
that the driver has learnt to scan the non-architecture dependent location
in addition to the architecture location dependent path, we can unify
the swiftmodule content in the SDK to a simpler layout. The layout now
is:
On Windows, it would be preferable to further remove the intermediate
platform as we have that information earlier in the path.
Subsequent work remains to now ensure that the package manager will
similarly allow the XCTest swift modules to collapse.
While in theory it is possible to create a multi-architecture import
library, it is valuable to support user-selectable SDK installation
which requires that the we create the import libraries on the fly for
the selected architectures. It is more convenient from a distribution
perspective to simply make the content static and as such continue to
use the architect dependent directory for the import library unlike the
swift module.
This is dependent on swiftlang/swift#42419.