Describe the feature
This mostly helps when a user installs v on macos via homebrew
When you install vlang through homebrew on mac the vroot tends to be something like /opt/homebrew/Cellar/vlang/<version>/bin which v-analyzer isn't able to find.
One could also add this path as the custom_vroot but it's likely to change whenever you update v.
It would be nice if the docs mentioned the command v symlink, which symlinks the v executable to a more common location.
v-analyzer seems to find the binary and standard library just fine once this is done.
Use Case
It wasn't immediately clear to me how to get v-analyzer to work and a section in the documentation would likely help others here as well
Other Information
No response
Describe the feature
This mostly helps when a user installs v on macos via homebrew
When you install vlang through homebrew on mac the vroot tends to be something like
/opt/homebrew/Cellar/vlang/<version>/binwhich v-analyzer isn't able to find.One could also add this path as the
custom_vrootbut it's likely to change whenever you update v.It would be nice if the docs mentioned the command
v symlink, which symlinks the v executable to a more common location.v-analyzer seems to find the binary and standard library just fine once this is done.
Use Case
It wasn't immediately clear to me how to get v-analyzer to work and a section in the documentation would likely help others here as well
Other Information
No response