Skip to content

Conversation

@fmeum
Copy link
Collaborator

@fmeum fmeum commented Aug 10, 2022

The solib directory is located within the subdirectory of the runfiles
directory corresponding to the workspace. Thus, if a binary is contained
in an external repository, its $ORIGIN relative rpath has to first
ascend to the runfiles directory and then descend into the workspace
directory.

Fixes #16003

Closes #16008.

PiperOrigin-RevId: 466634083
Change-Id: I4ada28b459f23f68a2091dbaad9147cfec2fbe43

Fixes #16028

The solib directory is located within the subdirectory of the runfiles
directory corresponding to the workspace. Thus, if a binary is contained
in an external repository, its $ORIGIN relative rpath has to first
ascend to the runfiles directory and then descend into the workspace
directory.

Fixes bazelbuild#16003

Closes bazelbuild#16008.

PiperOrigin-RevId: 466634083
Change-Id: I4ada28b459f23f68a2091dbaad9147cfec2fbe43
@fmeum fmeum marked this pull request as ready for review August 10, 2022 12:42
@fmeum fmeum requested a review from ShreeM01 as a code owner August 10, 2022 12:42
@ShreeM01 ShreeM01 merged commit e745468 into bazelbuild:release-5.3.0 Aug 10, 2022
@ShreeM01 ShreeM01 added the team-Rules-CPP Issues for C++ rules label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-Rules-CPP Issues for C++ rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants