Newer VBCC and LINE DEBUG file paths?

[Warty]

I updated my VBCC build from something from 2018, to the latest from phoenix.owl.de/downloads/vbcc.tar.gz (etc). I noticed that now the debug information in the HUNK files includes the full UNIX path of each source file, and not just the filename. When I try to debug in SAS/C CPR tool, it can't find the files, because the UNIX paths don't work of course.

Peeking in the hunk file, older tool produces something like this:
LINElich_king.c

New one like this:
LINE/Users/micahbly/dev/bbedit-workspace-amiga/LichKing-Amiga/lich_king.c

I confirmed by recompiling same code with my older version of VBCC, that the paths don't get written. I tried adding -strip-paths, but that doesn't produce a noticeable difference. Is there a new switch I should be using?

New build versions:
vbcc V0.9h (c) in 1995-2022 by Volker Barthelmann
vasm 1.9f (c) in 2002-2023 Volker Barthelmann
vlink V0.17a (c)1997-2022 by Frank Wille

Old build versions:
vbcc V0.9h pre (c) in 1995-2020 by Volker Barthelmann
vlink V0.16a (c)1997-2017 by Frank Wille
vasm 1.8c (c) in 2002-2018 Volker Barthelmann

[phx]

Originally Posted by Warty

debug information in the HUNK files includes the full UNIX path of each source file, and not just the filename. When I try to debug in SAS/C CPR tool, it can't find the files, because the UNIX paths don't work of course.

I guess I switched to the full absolute path to make debugging on the Amiga work from any directory. Otherwise you have to start your debugger from the project's compilation directory.

But for cross-compiling I admit that this is not ideal. A command line option might be the solution.

I tried adding -strip-paths, but that doesn't produce a noticeable difference.

This is not a vbcc problem. vbcc still writes the source file name from the command line into the assembler output. I changed vasm:

- 1.8e (28.12.18)
(...)
o output-hunk: Always try to include the full absolute source-path when
  writing LINE debug hunks (-linedebug option).

Is there a new switch I should be using?

With tomorrow's vasm source snapshot you may use

-noabspath

.
This option should probably go into the non-native vbcc config files, when working as expected.

[Warty]

Very cool. Will test whenever it's ready.