Skip to content

Conversation

compnerd
Copy link
Member

Rather than requiring the build tree for the dependencies, optionalise them. This allows us to build against an existing SDK or against the build tree. This flexibility allows us to change the build order when building the Windows toolchain against a SDK that is being built up. Without this change, we must provide a dispatch build tree which will inject the modulemap for the dispatch runtime which conflicts with the verison in the SDK that is being built against.

Rather than requiring the build tree for the dependencies, optionalise
them. This allows us to build against an existing SDK or against the
build tree. This flexibility allows us to change the build order when
building the Windows toolchain against a SDK that is being built up.
Without this change, we must provide a dispatch build tree which will
inject the modulemap for the dispatch runtime which conflicts with the
verison in the SDK that is being built against.
@compnerd
Copy link
Member Author

@swift-ci please smoke test

@compnerd
Copy link
Member Author

@swift-ci please test Linux platform

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