Skip to content
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.

Sign up for GitHub

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

Add note to emphasize replacing TARGET_TRIPLE #1250

Merged
merged 3 commits into from
Nov 6, 2021
Merged

Add note to emphasize replacing TARGET_TRIPLE #1250

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9fed073
Add note to emphasize replacing TARGET_TRIPLE
asquared31415 Nov 5, 2021
d700e88
Update suggested.md
asquared31415 Nov 6, 2021
02157ec
Make `TARGET_TRIPLE` use a `$` to signal placeholder
asquared31415 Nov 6, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/building/suggested.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,12 @@ you can write: <!-- date: 2021-09 --><!-- the date comment is for the edition be
in your `.vscode/settings.json` file. This will ask `rust-analyzer` to use
`x.py check` to check the sources, and the stage 0 rustfmt to format them.

> NOTE: Make sure to replace `TARGET_TRIPLE` in the `rust-analyzer.rustfmt.overrideCommand`
> setting with the appropriate target triple for your machine. An example of such
> a triple is `x86_64-unknown-linux-gnu`. An easy way to check the target triple
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> a triple is `x86_64-unknown-linux-gnu`. An easy way to check the target triple
> a triple is `x86_64-unknown-linux-gnu`. An easy way to check your target triple

> is looking in the `build` folder in the root of your rust clone after building the
> compiler at least once. It will have a folder with the same name as your target triple.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is easier:

Suggested change
> is looking in the `build` folder in the root of your rust clone after building the
> compiler at least once. It will have a folder with the same name as your target triple.
> is to run `rustc -vV` and check `host` of its output.


If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a
`.vim/coc-settings.json` and enter the same settings as above, but replacing
`editor.formatOnSave: true,` with
Expand Down