compile_commands.json and absolute paths in Windows

{
  "directory": "C:/cmake-vscode-embedded-sample/build/full-sim",
  "command": "C:\\mingw64\\bin\\gcc.exe -DCONFIG_FULL -DDEBUG -DPRINT_INTRO @CMakeFiles/hello.dir/includes_C.rsp -g3 -Wmissing-declarations -Wextra -Wall -Wlogical-op -Wjump-misses-init -Wno-missing-field-initializers -Wmaybe-uninitialized -Wuninitialized -Wundef -Wbad-function-cast -Wcast-align -Wcast-qual -Wfloat-equal -Wformat=2 -Wmissing-include-dirs -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls -Wsequence-point -Wshadow -Wstrict-prototypes -Wswitch -Wunreachable-code -Wunused-but-set-parameter -Wwrite-strings -std=gnu11 -g3 -funsigned-char -pedantic -o CMakeFiles\\hello.dir\\src\\main.c.obj -c C:\\cmake-vscode-embedded-sample\\src\\main.c",
  "file": "C:/cmake-vscode-embedded-sample/src/main.c",
  "output": "CMakeFiles/hello.dir/src/main.c.obj"
},

Is it normal to have paths with slash and not backslash? I’m using cmake.exe 4.0.3 installed from here (native Windows).

For me it’s just fine, but some native Windows tools could complain.

see The compile_commands.json is not usable with run-clang-tidy