-
Notifications
You must be signed in to change notification settings - Fork 206
[Toolchains] - look for tools relative to the executable path. #25
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
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.
Thanks for tackling this!
Just wanna make sure this does the right thing falling back @swift-ci please test |
d2c9d61
to
e53c79b
Compare
@swift-ci please test |
1 similar comment
@swift-ci please test |
…pecific behavior. FIX - some typos and parameter names. Merge branch 'master' into where-are-the-tools
Conflicts everywhere! It'll be good to get this up-to-date and merged now that #25 is in. Thank you! |
@swift-ci please test |
@swift-ci please test |
I saw some tests failing on Linux in the main swift project too. I think this can be a CI configuration issue. |
@swift-ci please test |
All issues have been resolved
Once swift-driver is installed in the Toolchain, we can look for tools right next to it's executable path, this help us to be more platform agnostic while locating the toolchain.
This is the first step in this direction, we will need to make this more robust to get rid of xcrun if possible, and get a proper linux implementation.
The other options are:
Shim LLVM's getMainExecutable method using
swift-lldb
, and expose the API fromlldbSwift
totools-support-core
, so other projects such asSwiftPM
would benefit from this.Try to implement something like LLVM's getMainExecutable method in
tools-support-core
. But I don't think this is 100 % feasible right now; this should be implemented in some low-level library such asLLVM
,swift-lldb
orFoundation
, to maintain projects asSwiftPM
andswift-driver
platform agnostic as possible.