Skip to content

Remove supports-path-mapping from CppLink by default - #804

Open
keith wants to merge 1 commit into
bazelbuild:mainfrom
keith:ks/remove-supports-path-mapping-from-cpplink-by-default
Open

Remove supports-path-mapping from CppLink by default#804
keith wants to merge 1 commit into
bazelbuild:mainfrom
keith:ks/remove-supports-path-mapping-from-cpplink-by-default

Conversation

@keith

@keith keith commented Jul 28, 2026

Copy link
Copy Markdown
Member

There are 2 major known issues with this today:

  1. When targeting macOS the debug info paths stored in the binaries are
    invalid, since they encode the literal bazel-out/cfg
  2. Paths in environment variables configured in the toolchain are not
    path mapped today. They should be in a future bazel release, but the
    current fix will also only fix direct File objects not more complex
    cases

If users are ok with these 2 limitations they should enable this
manually with --modify_execution_info=CppLink=+supports-path-mapping

There are 2 major known issues with this today:

1. When targeting macOS the debug info paths stored in the binaries are
   invalid, since they encode the literal `bazel-out/cfg`
2. Paths in environment variables configured in the toolchain are not
   path mapped today. They should be in a future bazel release, but the
   current fix will also only fix direct File objects not more complex
   cases

If users are ok with these 2 limitations they should enable this
manually with `--modify_execution_info=CppLink=+supports-path-mapping`
@keith
keith requested review from c-mita, pzembrod and trybka as code owners July 28, 2026 19:31
@trybka

trybka commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

@lilygorsheneva

@lilygorsheneva

Copy link
Copy Markdown
Collaborator

I realized I need to put this behind a feature flag anyway (there's a specific test target type we have issues with); I'll have a change out for review this week; if you're ok waiting.

@keith

keith commented Jul 28, 2026

Copy link
Copy Markdown
Member Author

yea i think it's fine as long as we make it for the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants