-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backslashes in include paths not processed properly #120
Comments
ydamigos
added a commit
to ydamigos/compiledb
that referenced
this issue
Oct 26, 2022
Unescape input to bashlex parser. It should address issues nickdiego#124, nickdiego#120 Signed-off-by: Ioannis Damigos <[email protected]>
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 <[email protected]>
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 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: