-
-
Notifications
You must be signed in to change notification settings - Fork 817
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
clang c++20 modules missing information in compile_commands.json exported #1167
Comments
Yes, it is not currently supported, maybe I will consider supporting it on 2.5.2 related issue. #1148 |
FYI, I just found probably a simpler way to get things work. Current UPDATE: there is a drawback. The file name must be exactly the same with the module name, or clangd still cannot found. The previous way should be better. |
ok, thanks. I will improve c++20 modules on 2.5.2. In addition, I will also support c++20 modules for gcc. |
we have supported it, you can try However, vscode and other editor/ide should not yet support complie_commands with c++modules. |
but vscode and other some ide maybe still not support compile_commands.json with c++modules. |
I have made some try with However, I have to admit that the whole module thing is still not useable with |
yes, and I have merged it now. |
Describe the bug
In current version, the
compile_commands.json
file generated with xmake when using clang11 c++20 modules lost the options"-fmodule-file=xxx.pcm
, which would make clangd cannot find the module I am importing.Expected behavior
The
compile_commands.json
should add the option mentioned.Error output
If applicable, please add verbose the errors output to help us analyze your problem.
Related Environment
Please provide compiling and running environment information:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: