Fix RMW_LIBRARY_PATH define in presence of transitions

[lalten]

This fixes the below error

unknown file: Failure
C++ exception with description "Failed to deserialize ROS message.: failed to load shared library 'external/ros2_rmw_cyclonedds/librmw_cyclonedds.so' due to dlopen error: external/ros2_rmw_cyclonedds/librmw_cyclonedds.so: cannot open shared object file: No such file or directory, at external/ros2_rcutils/src/shared_library.c:96, at external/ros2_rmw_implementation/rmw_implementation/src/functions.cpp:90" thrown in the test body.

Which you will get when transitions (e.g. via with_cfg.bzl) are at play, because the k8-fastbuild and friends will not be correct anymore, it has to be k8-fastbuild-ST-61f4e3852c4b or similar, depending on configuration.

Using ../ instead is always correct because of the runfiles structure at runtime.

[mvukov]

rootpath shouldn't have k8-fastbuild in it AFAIK.

We touched this in

• Do not rely on external symlink for RMW_LIBRARY_PATH #65 and then in
• Assemble RMW_LIBRARY_PATH with rootpath #66

I'd like to learn more about your usecase.

BTW, do you patch rmw_implementation with_cfg.bzl locally?

[lalten]

I added a failing test in ca7da17:
https://github.com/mvukov/rules_ros2/actions/runs/13606301154/job/38038169533?pr=446#step:5:61

and fixed it by using ../ instead of $(rootpath in 00f4065

[lalten]

yes this isn't the latest release, but newer ones seem to cause issues with struct members of @bazel_features not being available when building in Workspace mode

[mvukov]

Would --nolegacy_external_runfiles help in the first place (mentioned in #65 )? (that is a recommended flag, we should have it in .bazelrc eventually) . With that flag I think we should just get ../ros2_rmw_cyclonedds/librmw_cyclonedds.so.

[lalten]

Would --nolegacy_external_runfiles help in the first place (mentioned in #65 )? (that is a recommended flag, we should have it in .bazelrc eventually) . With that flag I think we should just get ../ros2_rmw_cyclonedds/librmw_cyclonedds.so.

True, this does indeed help. But requiring this to be set is a hard sell to downstream consumers who may have a lot of migration work ahead of them to support this flag being flipped -- especially when just using ../ also makes this work regardless of --(no)legacy_external_runfiles