-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Runtimes: support installing the swiftdoc for the modules #81425
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
@swift-ci please smoke test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to make it a separate function or should we roll it into part of the module installation? Are there libraries where we don't want to include the swiftdoc when we do include the module?
Good question. I don't know the best answer here. I think that we do always want to install the swiftdoc. However, I don't think that this should be part of the I can see the value in keeping it separate - |
@swift-ci please test Windows platform |
@swift-ci please smoke test |
Extract the `install_swift_interface` function into a new file. This is always invoked to perform the installation of the Swift interfaces as well as the binary module. Additionally, it prepares for a future refactoring which will also install the swift documentation interface.
This is part of the development component for the module and is part of the interface definition. This content is consumed by the user during development.
@swift-ci please smoke test |
Add support to install the swiftdoc into the installed image. This is required to allow us to package up the runtime on Windows.