Skip to content

Conversation

compnerd
Copy link
Member

This pull request introduces conditional support for including a legacy Windows SDK in the build and installer process. The main change is the addition of the IncludeLegacySDK property, which controls whether legacy SDK components are included. The build scripts, installer projects, and configuration files have been updated to selectively include legacy or experimental SDK files and components based on this property.

Conditional legacy SDK support

  • Added the IncludeLegacySDK property to Directory.Build.props and passed it through build constants to enable conditional inclusion of legacy SDK components. [1] [2]
  • Updated installer.wixproj and windows.wixproj to conditionally add references to legacy SDK project files and components when IncludeLegacySDK is set to true. [1] [2]
  • Modified harvesting and inclusion of Swift shims and other SDK files to use either the legacy or experimental SDK paths based on the property. [1] [2]
  • Updated the installer chain and package definitions in installer.wxs to select between legacy and shared MSI packages depending on the legacy SDK flag. [1] [2]

Installer and component configuration changes

These changes make it possible to build and install either the legacy or experimental Windows SDK by simply setting the IncludeLegacySDK property, improving flexibility and easing the transition to the new SDK.

This moves the legacy RTL packaging into a subdirectory as preparation
for resection.
This adjusts the packaging to allow exclusion of the legacy SDK. This is
a preparatory step towards removing the legacy SDK from the build and
the packaging.
Adjust the package authoring to use separate paths as we prepare to
eject the legacy SDK.
Adjust the feature set to extract platform support from the SDK content.
This allows us to have the platform specific libraries (XCTest, Testing)
isolated from the SDK content. It also allows us to temporarily share
the features across the legacy and experimental SDKs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant