Skip to content

Command to get toolchain path #491

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

Closed
alexreg opened this issue May 23, 2016 · 3 comments
Closed

Command to get toolchain path #491

alexreg opened this issue May 23, 2016 · 3 comments

Comments

@alexreg
Copy link

alexreg commented May 23, 2016

The old multirust (script) had a ctl command that allowed you to get the default toolchain, active toolchain, and path for any given toolchain. Is there a way to do this in rustup? If not, it would be a nice feature to add, for scripting in particular.

@brson
Copy link
Contributor

brson commented Jun 3, 2016

There's no way to do this presently. ctl was an implementation detail of multirust and I didn't expect it to be used for scripting. If you want the active toolchain path you can run rustup which rustc and derive it from that. If you need more precise information I'm interested to know what exactly and for what purpose.

@alexreg
Copy link
Author

alexreg commented Jun 3, 2016

Yeah, that’s the solution I was considering. My use case was actually for a script for viewing Rust man pages for the current toolchain.

On 3 Jun 2016, at 22:20, Brian Anderson [email protected] wrote:

There's no way to do this presently. ctl was an implementation detail of multirust and I didn't expect it to be used for scripting. If you want the active toolchain path you can run rustup which rustc and derive it from that. If you need more precise information I'm interested to know what exactly and for what purpose.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #491 (comment), or mute the thread https://github.com/notifications/unsubscribe/AAEF3OUIBJDzozy4HsMRcDT--6MghxJ0ks5qIJqngaJpZM4IkHOY.

@Diggsey
Copy link
Contributor

Diggsey commented May 4, 2017

Dupe of #450

@Diggsey Diggsey closed this as completed May 4, 2017
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

No branches or pull requests

3 participants