Open aelam opened 7 years ago
@aelam do you mean to use homebrew to install the binary into the system PATH, then you do not need to config this in vscode?
as I mentioned in the README of sde, the Swift ABI is not stable. The binary is fragile. It is very likely that the binary does work in some time but does not works after serveral days. You can update this binary but it still does not work for the old swift (standard) libraries. The true solution is that your swift (standard) libraries should be matched with its linked binary now.
but, maybe we can consider to pin a binary after 3.1 released? :eyeglasses:
Maybe you can provide a brew file as an easier alternative way. make install/upgrade easier, and also it can be used in the future
On 17 Mar 2017, at 11:47 AM, Jin Mingjian notifications@github.com wrote:
but, maybe we can consider to pin a binary after 3.1 released? 👓
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I'm not understanding the logic that because it needs to be updated frequently and version matching is important we shouldn't enable a package manager that makes these two things super easy?
"swift.path.sourcekite": "/path/to/repo/sourcekite/.build/debug/sourcekite" Set the path as
/path/to/repo/...
is kinda pain for meIf it supports homebrew, things would be easier