How to use managedbuilder in a headless CDT plugin for eclipse?

[beryozavv]

Hello. Can you provide examples of how to use ManagedBuilder in the headless CDT plugin for Eclipse? Or how to configure cproject so that indexing is successful and node resolving is successful?
When using the org.eclipse.cdt.managedbuilder.core dependency in the headless Eclipse plugin, errors immediately appear that the Workbench, SWT, and other UI components are not running. If I do not use ManagedBuilder, then nothing will be resolved as a result of indexing a simple test c++ cmake project. Here is an example of headless plugin logs without ManagedBuilder:
!MESSAGE Indexed 'ThirdCmakeProject' (3 sources, 1 headers) in 0.042 sec: 50 declarations; 444 references; 6 unresolved inclusions; 0 syntax errors; 93 unresolved names (16%)
Unresolved: std::string at C:\beryozavv\CPP examples workspace\ThirdCmakeProject\ThirdCmakeProject.cpp:13 (org.eclipse.cdt.internal.core.dom.parser.ProblemBinding)
Unresolved: string at C:\beryozavv\CPP examples workspace\ThirdCmakeProject\ThirdCmakeProject.cpp:13 (org.eclipse.cdt.internal.core.dom.parser.ProblemBinding)
Unresolved: std::move at C:\beryozavv\CPP examples workspace\ThirdCmakeProject\ThirdCmakeProject.cpp:16 (org.eclipse.cdt.internal.core.dom.parser.ProblemBinding)
Unresolved: move at C:\beryozavv\CPP examples workspace\ThirdCmakeProject\ThirdCmakeProject.cpp:16 (org.eclipse.cdt.internal.core.dom.parser.ProblemBinding)
Unresolved: std::cout at C:\beryozavv\CPP examples workspace\ThirdCmakeProject\ThirdCmakeProject.cpp:19 (org.eclipse.cdt.internal.core.dom.parser.ProblemBinding)