Jeroen Ketema

> If there is an opened issue for this to be folded at some point, I'd like to follow it. That's an internal issue, so unfortunately I cannot share it....

Apologies for the slow response. I looked at this briefly, but ran into - what seemed to be - some quite fundamental problems. I'll try to have another look soon.

> this problem basically bites me on every query Understood. > Is there any update on the problem or fix and a potential eta or Not really. It depends a...

@skliper I'm not able to reproduce the behaviour you're describing. I built the library per the instructions near the bottom of the readme: ``` mkdir build_osal cd build_osal cmake -DOSAL_SYSTEM_BSPTYPE=generic-linux...

Thanks for your question. To diagnose this further we'll need at least the `build-tracer.log` file created during the build. This file can be found in the `D:\chromium\99.0.4844.84\db\log`. You might also...

Thanks for the log. Could you also share the output of `d:\chromium\99.0.4844.84\src\third_party\llvm-build\release+asserts\bin\clang-cl.exe -Xclang -dM -E SomeEmptyFile.cpp`, where `SomeEmptyFile.cpp` is some empty file you should create.

Note that I slightly updated the command in the previous comment.

Thanks. This looks ok. For some reason we are not picking up on the `#define _MSC_VER ...` in that output stopping the extraction from running. This is the `Command-line error:...

Thanks. This also looks ok. I'm slightly puzzled by this. I think we need to try running codeql slightly differently unpacking the steps `database create` does under the hood. Instead...

Thanks. This seems to be an omission in our extractor code. We're not propagating the value of `_MSC_VER`. I think this should be easy to fix.