Fix refresh_compile_commands target.

[kentonv]

It appears to me that this select statement in rust-deps/BUILD.bazel is incorrectly using absolute paths to targets that aren't located at the root, but rather located within the same module. Fixing them to be local targets seems to make refresh_compile_commands now work. However, I'm confused why this didn't cause a broader breakage so I'm unsure if I totally understand what's going on here.

Fixes #16

[jasnell]

Makes things work for me but still not 100% what's going on with all this. Good to get @mrbbot sign off first.

[mrbbot]

Ah, using relative paths here makes way more sense. 🙂 I'm also unsure why this didn't break other things though. 😕

Just to note, when I try to run bazel run //:refresh_compile_commands on my M1 Mac I see the following errors. The command still succeeds, and compile_commands.json is still generated.

In file included from external/capnp-cpp/src/capnp/c++.capnp.c++:4:
external/capnp-cpp/src/capnp/c++.capnp.h:10:2: error: "Version mismatch between generated code and library headers.  You must use the same version of the Cap'n Proto compiler and library."
#error "Version mismatch between generated code and library headers.  You must use the same version of the Cap'n Proto compiler and library."
 ^
1 error generated.
...lots more of these...

I get what this error is saying, but I'm confused why multiple versions of Cap’n Proto are being used here. Is it trying to use the version on my PATH?

[kentonv]

@mrbbot Hmm I'm surprised that refresh_compile_commands needs to actually run the compiler, and it's worrying that it seems to be picking up the system-installed capnp headers and letting them take precedence over the local ones... hopefully this isn't resulting in incorrect compile commands.