Initial compatibility with stock toolchain #722
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing off AnyLayer from stock toolchains.
dan-zheng
approved these changes
Dec 17, 2020
pschuh
approved these changes
Dec 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This provides the needed Numerics dependency, as well as missing _Differentiation imports, to support building while using a stock toolchain with swift-apis. For now, the AnyLayer type has been gated off from the stock toolchain until it can be reworked to support the new VectorProtocol.
To build this successfully under Swift Package Manager with the stock toolchain, you'll need to provide the
TENSORFLOW_USE_STANDARD_TOOLCHAINflag:This is needed to avoid a conflict caused by the use of Numerics in the stock toolchain. CMake should detect this automatically, and does not require any additional command-line options.