Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

🐛 error: no bin target named rome_lsp #3138

Closed
1 task done
lgarron opened this issue Aug 31, 2022 · 5 comments
Closed
1 task done

🐛 error: no bin target named rome_lsp #3138

lgarron opened this issue Aug 31, 2022 · 5 comments
Labels
S-To triage Status: user report of a possible bug that needs to be triaged

Comments

@lgarron
Copy link

lgarron commented Aug 31, 2022

I'm trying to follow https://github.com/rome/tools/blob/main/CONTRIBUTING.md#language-server-and-vs-code-extension-development so I can test #3089 and #3088 (without waiting a week).

Environment information

macOS 12.5.1
M1 Pro MacBook Pro

What happened?

git clone https://github.com/rome/tools
cd tools

cargo build --bin rome_lsp

Result:

error: no bin target named `rome_lsp`

Expected result

The instructions result in a rome_lsp binary.

Note that cargo build --bin rome works — it's only the rome_lsp target that fails for me.

Code of Conduct

  • I agree to follow Rome's Code of Conduct
@lgarron lgarron added the S-To triage Status: user report of a possible bug that needs to be triaged label Aug 31, 2022
@lgarron
Copy link
Author

lgarron commented Aug 31, 2022

It seems that rome_lsp might be a "lib" and not a "bin"?

run: cargo build -p rome_bin --release --target ${{ matrix.target }}

This works, but doesn't create a binary.

cargo build -p rome_bin --release

Taken from

@lgarron lgarron changed the title 🐛 error: no bin target named rome_lsp`` 🐛 error: no bin target named rome_lsp` Aug 31, 2022
@lgarron lgarron changed the title 🐛 error: no bin target named rome_lsp` 🐛 error: no bin target named rome_lsp Aug 31, 2022
@lgarron lgarron changed the title 🐛 error: no bin target named rome_lsp 🐛 error: no bin target named rome_lsp` Aug 31, 2022
@lgarron lgarron changed the title 🐛 error: no bin target named rome_lsp` 🐛 error: no bin target named rome_lsp Aug 31, 2022
@lgarron
Copy link
Author

lgarron commented Aug 31, 2022

Okay, it looks like I should maybe actually use the rome binary path directly as rome.lspBin?

Unfortunately, installing both the built .vpix (which I had to do using the UI?) and setting rome.lspBin doesn't seem to have fixed #3088 (although #3089 no longer breaks).

@ematipico
Copy link
Contributor

There's a PR to update that section. #3136

@ematipico
Copy link
Contributor

Also, if you're now using the built binary, you can now inspect the logs: https://rome.github.io/tools/rome_bin/index.html#logs

@ematipico
Copy link
Contributor

The section has been updated!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
S-To triage Status: user report of a possible bug that needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants