clang_complete

clang_complete copied to clipboard

Current options:

• cc_args.py
• ake VERBOSE=1 to show the compile command and then edit the .clang_complete manually.

compile_commands.json?

cmake and meson both automatically generate that file in the build directory for the benefit of clangcheck...

@tbodt Thanks, I'll look into that

I get compile_commands.json working. The default option doesn't take compile_commands.json.

I plan to change the compile option loading process. I think this version would be more meaningful:

• look for .clang_complete
• If not found, fallback to compile_commands.json, and possibly build/compile_commands.json as a common convention.
• If not found, fallback to &path variable

🎉

I think there should be an option you can set to customize the path to compile_commands.json

Wouldn't it be more natural to put compile_commands.json in the highest priority, since it specifies the CFLAGS for every source file independantly? If a specific file is not found in compile_commands.json, we can fallback to .clang_complete as a project-wise default setting.

Hi

I'm deprecating this repo.

Try https://github.com/roxma/ncm-clang instead.

Nice job! Thank you! @roxma