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".
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".