-
Notifications
You must be signed in to change notification settings - Fork 315
[5.1] Update with changes from master #145
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
Merged
benlangmuir
merged 122 commits into
swiftlang:swift-5.1-branch
from
benlangmuir:merge-51
Aug 17, 2019
Merged
[5.1] Update with changes from master #145
benlangmuir
merged 122 commits into
swiftlang:swift-5.1-branch
from
benlangmuir:merge-51
Aug 17, 2019
Conversation
This file contains hidden or 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
Add Windows Support to SKSupport
Use SPM UserToolchain. …
`npm audit fix`
[vscode] Update dependency on vscode module
... to match the style of the other editor instructions.
…t-symbol Implement document symbol request
Add instructions for Theia Cloud IDE
Add extra -Xcxx to docs, otherwise doesn't run command
Embrace Swift.Result in place SwiftPM.Basic.Result
Implement color presentation
…orts Remove `@testable import` and `-enable-testing`
make project.json spec-compliant by removing a trailing comma
In preparation for looking for toolchain next to the sourcekit-lsp binary, teach toolchain loading to find the info plist even if we are using the path `Foo.xctoolchain/usr/bin` instead of `Foo.xctoolchain`.
When the ToolchainRegistry is used in code embedded into a toolchain, we want to prefer that toolchain over any other search paths other than the explicit SOURCEKIT_TOOLCHAIN_PATH environment.
When sourcekit-lsp is embedded inside a toolchain, use its main bundle path as the install path to have the toolchain registry prefer that toolcahin.
There is not guarantee that the toolchain.path contains `usr/bin`. Instead, look at the diretory containing `swiftc`.
…lchain [sourcekit-lsp] Prefer containing toolchain if applicable
[test] Regenerate linuxmain
Fix deprecation warnings
When invoked with the `install` action, build-script-helper.py will rsync the produced sourcekit-lsp to the toolchain's bin directory. On Linux, we add an extra relative rpath to find the swift corelibs (unfotunately we currently have no way to remove the absolute rpath; the same is true for all other swift-built binaries in the toolchain). On macOS, we replace the rpath.
Swift-build was logging some extra information to stdout, causing incorrect calculation of the bin dir.
Handy for local development if you don't want to test with swift's full build.
[build-script] Add installation support for sourcekit-lsp
Separate toolchain discovery from build settings
swiftlang/indexstore-db#51 @swift-ci please test |
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.
Sync up with sourcekit-lsp master to get install support and recent bug fixes.