Building the rustup binary

I'm currently working on a PR to solve this issue which I reported.

TL;DR I want to add a flag to rustup component list to only show installed components so that some automation I'm using will be able to tell what is installed so it only adds components when they are not already present.

When I run cargo build, I only get a rustup-init binary and not the actual rustup binary itself. I'd like to test my work.

Is there some special magic I need to do in order to be able to build the rustup binary?

I believe that rustup-init is the same binary as rustup. It looks at its name to determine if it should run in install mode or normal mode.

3 Likes

Interesting. This does seem to be the case! Thank you! Perhaps I should PR some documentation into the README :thinking:

1 Like