Kevin Greene

Thank you for taking the time to write out a thorough explanation. I believe I understand how the runfiles layout is structured, and it makes sense what you're saying. I...

Also here is a fork where I am playing around with some ideas: https://github.com/kgreenek/rules_ros2/commit/85b75f46567a483059a4176888c7b5ec538cd181

I'd like to give this a gentle bump because it is becoming increasingly painful for me. I am distributing scripts (i.e. python binaries) to an external partner for them to...

Friendly bump. If the library `uniform_bspline_eigen` were available, that would make this package a lot more useful :) As it is, using this library isn't possible without reimplementing large chunks...

I ran into this exact issue too. My work-around is to return a shared_ptr from my factory function.

I found a work-around and a clue! Workaround: After running `bazel run //:refresh_compile_commands`, you have to run `bazel build //...` again. This fixes the bazel cache. It appears running refresh_compile_commands...

I dug a bit deeper and found that almost all of the symlinks in the external execroot cache directory are deleted after running `bazel run //:refresh_compile_commands`. In my case I...

This issue looks related: https://github.com/bazelbuild/bazel/issues/10680

I confirmed that if I don't invoke the refresh_compile_commands script with `bazel run`, then I do not see those errors. I.E. I do this: ``` bazel build //... BUILD_WORKSPACE_DIRECTORY=$PWD ./bazel-bin/refresh_compile_commands...

This is partially a duplicate, but my PR also added support for symlinks, in addition to the TreeArtifact implementation. I'll rework mine when I have time and send a new...