Some tools will record the path of the source files in their output.

Most compilers write the path of the source in the debug information in order to locate the associated source files.

Some tools have flags (like gzip’s -n) that prevent them from writing the path in their output. Proposing patches to add a similar feature in other tools might be sufficiently easy.

In most cases however, post-processing is required to either remove the build path or to normalize it to a predefined value.

For the specific case of DWARF symbols, there is currently no good tool to change them to a pre-determined value after a build1. A work-around is to define the build path as part of the build environment.

This is also problematic because this will also apply to intermediate source files that other tools generate. As they typically will use random file names, having a fixed build path is not enough in such cases.

  1. debugedit can replace the path used at build time by a predefined one but it does that by rewriting bytes in place. As this does not reorder the hash table of strings, the resulting bytes are still depending on the original build path.