You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are quite a few options available for `--remap-path-scope`. Not all of them are expected to have meaningful use-cases in their own right.
293
+
Some are only added for completeness, that is, the behaviour of `--remap-path-prefix=all` (or the original `--remap-path-prefix` on its own) is
294
+
the same as specifying all individual scopes. In the future, we expect some of the scopes to be removed as independent options, while preserving
295
+
the behaviour of `--remap-path-prefix=all` and the stable `--remap-path-prefix`, which is "Remap source names in all output".
296
+
297
+
-`macro` is primarily meant for panic messages embedded in binaries.
298
+
-`diagnostics` is unlikely to be used on its own as it only affects console outputs, but is required for completeness. See [#87745](https://github.com/rust-lang/rust/issues/87745).
299
+
-`unsplit-debuginfo` is used to sanitise debuginfo embedded in binaries.
300
+
-`split-debuginfo` is used to sanitise debuginfo separate from binaries. This is may be used when debuginfo files are separate and the author
301
+
still wants to distribute them.
302
+
-`split-debuginfo-path` is used to sanitise the path embedded in binaries pointing to separate debuginfo files. This is likely needed in all
303
+
contexts where `unsplit-debuginfo` is used, but it's technically a separate piece of information inserted by the linker, not rustc.
304
+
-`object` is a shorthand for the most common use-case: sanitise everything in binaries, but nowhere else.
305
+
-`all` and `true` preserves the documented behaviour of `--remap-path-prefix`.
0 commit comments