MSYS2 QtCreator Clangd code analysis can not find mm_malloc.h problem remedy

Recently, msys2 was upgraded in the computer room of the school. I encountered the code prompting problem of QtCreator. It is not completely solved. Because I have to go to class, a temporary remedy is adopted.

1. Phenomenon

Upgrade msys2 msys64, found that there is a problem with the parsing code of QtCreator clangd, prompting that mm_malloc.h cannot be found, similar to:

In include file : 'mm_malloc.h' file not found

Although it does not affect the compilation and debugging, it is very uncomfortable.

2. Preliminary Resolution

This error is weird.clangd is an analyzer that is supposed to automatically find header files.Open the folder and find that mm_malloc.h exists, and it is under the clang folder.

The problem should be in the configuration of clangd.When clangd analyzes the project of a third-party compiler (such as gcc), it will not associate the include of clang, which causes this problem.The correct solution is to manually specify the path for clangd, but it will not be able to find where the configuration file is placed for a while.See clangd help, it should be written in a config.Well, first use the built-in code analyzer and close the clangd option:

3. Further resolution

After the initial solution, the analysis error is gone, but there are a lot of useful tips missing.
We create a blank mm_malloc.h in the include folder of gcc and associate it with the real mm_malloc.h.If it's Linux, the support link would be awesome.Windows, or write include it.

//mm_malloc.h in mingw64/include#include "../lib/clang/14.0.4/include/mm_malloc.h"

After this setting, open the clangd option, and the original failure no longer occurs.

4. Insufficient

This method obviously won't work after upgrading clang.Because clang's include path has a version number of 14.0.4.This problem should be caused by using clang to analyze the gcc project.To solve the bell, it is necessary to be the bell person. I don't know that the development team of Qt for msys2 has noticed this problem.