We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello, I tried using compiledb on Windows and it looks like backslashes in include paths get deleted.
compiledb
Here's a make output:
make
make: Entering directory `C:/projects/test/build' echo 'Building file: ../test.c' echo 'Invoking: GNU ARM C Compiler' arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -I"C:\projects\test" -o "test.o" "../test.c" echo 'Finished building: ../test.c' echo ' ' make: Leaving directory `C:/projects/test/build'
Note that this has been manually sanitized from an original.
Resulting compile_commands.json after running compiledb --parse:
compile_commands.json
compiledb --parse
[ { "directory": "C:\\projects\\test\\build", "arguments": [ "arm-none-eabi-gcc", "-mcpu=cortex-m33", "-mthumb", "-IC:projectstest", "-o", "test.o", "../test.c" ], "file": "../test.c" } ]
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.
-I
The text was updated successfully, but these errors were encountered:
compiledb/parser: Unescape input to bashlex parser
5429536
Unescape input to bashlex parser. It should address issues nickdiego#124, nickdiego#120 Signed-off-by: Ioannis Damigos <[email protected]>
aea17ec
0a7f65b
No branches or pull requests
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: