Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Flag flip for `--experimental_sibling_repository_layout` and `--legacy_external_runfiles`
See original GitHub issueWe are changing the way external repositories are handled: they will be a sibling of the main repository instead living in the external/ directory under it, both in the execroot and in runfiles trees.
That is, files in them will be accessible at ../$REPO instead of external/$REPO.
This is a tracking bug for the imminent flag flip and a place to list tips for the migration and things that broke.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
incompatible_enforce_config_set...
This flag starts the process of removing the distinction. ... visibility explicitly if they'll be used anywhere outside their own package.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FYI, @TLATER , https://github.com/bazelbuild/bazel/pull/16008 appears to fix the failed test for me! Very exciting.
@oquenchil Do you have any comments about how C++ rules set up the shared library path? (see above)
@lberki @jin The commit in question was authored by someone on the Roboleaf team (IIRC) who has since left the team. Do you have any comments on the breakage?