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
Unescape input to bashlex parser.
It should address issues nickdiego#124, nickdiego#120
Signed-off-by: Ioannis Damigos <ioannis.damigos.uj@renesas.com>
Unescape input to bashlex parser.
It should address issues nickdiego#124, nickdiego#120
Signed-off-by: Ioannis Damigos <ioannis.damigos.uj@renesas.com>
marzojr
pushed a commit
to marzojr/compiledb
that referenced
this issue
Feb 22, 2024
Unescape input to bashlex parser.
It should address issues nickdiego#124, nickdiego#120
Signed-off-by: Ioannis Damigos <ioannis.damigos.uj@renesas.com>
Hello, I tried using
compiledb
on Windows and it looks like backslashes in include paths get deleted.Here's a
make
output:Note that this has been manually sanitized from an original.
Resulting
compile_commands.json
after runningcompiledb --parse
:This output has also been manually sanitized but should get the point across.
Note how the backslashes in the
-I
parameter are not present. Obviously, the result is not a valid path.The text was updated successfully, but these errors were encountered: