You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to specify an alternative compiler path? My project uses its own compiler but clang-uml picks up the compiler installed on the system, which is older and doesn't recognize the newer headers (utility, optional, chrono, ..).
The text was updated successfully, but these errors were encountered:
@aka-mj Typically, compiler path should be set properly in your compile_commands.json as the first argument of each compile command.
If it is, and the compiler is GCC-compatible, you can run clang-uml with --query-driver . argument, which will extract the necessary include paths from the compiler and add them to the compile commands.
If your compile_commands.json for some reason does not have the right compiler, you can pass a custom compiler in the --query-driver option, e.g.:
$ clang-uml --query-driver arm-none-eabi-g++
Furthermore, if this doesn't help, you can manually add or remove compilation flags in the .clang-uml config, e.g.:
Is it possible to specify an alternative compiler path? My project uses its own compiler but clang-uml picks up the compiler installed on the system, which is older and doesn't recognize the newer headers (utility, optional, chrono, ..).
The text was updated successfully, but these errors were encountered: