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.

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

Debugger, error messages go to file in bazel exec_root #5

Open
tmandry opened this issue Apr 24, 2018 · 0 comments · May be fixed by #4
Open

Debugger, error messages go to file in bazel exec_root #5

tmandry opened this issue Apr 24, 2018 · 0 comments · May be fixed by #4
Labels
bug Something isn't working
Milestone

Comments

@tmandry
Copy link
Owner

tmandry commented Apr 24, 2018

bazel sets up a junction so that file paths in its exec_root (where it runs the compiler) point to the files/directories in the original source directory.

However, Visual Studio doesn't realize this, and thinks the files at the different paths are distinct. This breaks IntelliSense, modify/save behavior, etc when in the exec_root "upside-down".

@tmandry tmandry added the bug Something isn't working label Apr 25, 2018
@tmandry tmandry added this to the 0.1.0 milestone Apr 25, 2018
@tmandry tmandry linked a pull request Apr 25, 2018 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant