如何让ALE与Windows/Cygwin和tricore混合工作--gcc？

Question

编辑:我在Windows 10上运行，使用gvim，但整个项目是用Cygwin构建的。我使用的编译器是tricore-gcc。我费了很大劲才设法构建了一个compile_commands.json文件，这个文件显然工作得很好(如果我使用一个不能解析compile_commands.json的linter，我会立即在第一个#include上出现错误，而如果我使用clangtidy，这样的错误就会消失)。

尽管如此，我还是尝试通过删除一些;或}来修改.c文件，以检查linter是否正常工作，但什么也没有发生。

我试图通过从Powershell和Cygwin运行ALEInfo中显示的命令来进行一点调试，但是我得到了以下错误：

C:\> clang-tidy C:\Project1\Root\software\ComponentONE\src\fileA.c -p C:\Project1\Root
Skipping C:\Project1\Root\software\ComponentONE\src\fileA.c. Compile command not found.

我还尝试通过用\更改/来调整compile_commands.json (与从Powershell运行的命令相同)，我尝试用gcc替换tricore-gcc，等等，但我总是得到与上面相同的错误。

如果我只是运行

C:\>clang-tidy.exe
clang-tidy.exe: Not enough positional command line arguments specified!
Must specify at least 1 positional arguments: See: C:\Program Files (x86)\LLVM\bin\clang-tidy.exe -help

这意味着可以识别clang-tidy。

最后，如果我运行真正的编译器命令：

C:\> tricore-gcc.exe (various flags) C:\Project1\Root\software\ComponentONE\src\fileA.c

无论是从Powershell还是Cygwin，我都没有得到任何错误。

它跟随我的ALEInfo

 Current Filetype: c
Available Linters: ['cc', 'ccls', 'clangd', 'clangtidy', 'cppcheck', 'cquery', 'flawfinder']
   Linter Aliases:
'cc' -> ['gcc', 'clang']
  Enabled Linters: ['clangtidy']
  Ignored Linters: []
 Suggested Fixers: 
  'astyle' - Fix C/C++ with astyle.
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'clangtidy' - Fix C/C++ and ObjectiveC files with clang-tidy.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:

let g:ale_c_always_make = 0
let g:ale_c_build_dir = ''
let g:ale_c_build_dir_names = ['build', 'bin']
let g:ale_c_clangtidy_checks = []
let g:ale_c_clangtidy_executable = 'clang-tidy'
let g:ale_c_clangtidy_extra_options = ''
let g:ale_c_clangtidy_options = ''
let g:ale_c_parse_compile_commands = 1
let g:ale_c_parse_makefile = 0
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = 100
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = 50
let g:ale_disable_lsp = 0
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {'c': ['clangtidy'], '*': ['remove_trailing_lines', 'trim_whitespace']}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'normal'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['clangtidy']}
let g:ale_linters_explicit = 0
let g:ale_linters_ignore = {}
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_root = {}
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_sign_highlight_linenrs = 0
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:
(executable check - success) clang-tidy
(finished - exit code 0) 'cmd /s/c "clang-tidy C:\Project1\Root\software\ComponentONE\src\fileA.c -p C:\Project1\Root"'
<<<NO OUTPUT RETURNED>>>

还有我的_vimrc

let g:ale_linters = {
\ 'c': ['clangtidy'],
\}
let g:ale_fixers = ['clangtidy']
let g:ale_fixers={
\   'c': ['clangtidy'],
\   '*': ['remove_trailing_lines', 'trim_whitespace'],
\}

以及我的compile_commands.json文件的一个摘录：

{
  "directory": ".",
  "command": "c:/Hightec/tricore/v4.6.6.1/bin/tricore-gcc.exe (number of flags) -c software/ComponentONE/src/fileA.c",
  "file": "software/ComponentONE/src/fileA.c"
},

如果我在vim中运行pwd，我会得到C:\Project1\Root

Answer 1

修复了！

我不得不这样修改compile_commands.json文件：

{
  "directory": "C:/Project1/Root",
  "command": "c:/Hightec/tricore/v4.6.6.1/bin/tricore-gcc.exe (number of flags) -c software/ComponentONE/src/fileA.c",
  "file": "software/ComponentONE/src/fileA.c"
},

或者以这种方式

{
  "directory": ".",
  "command": "c:/Hightec/tricore/v4.6.6.1/bin/tricore-gcc.exe (number of flags) -c software/ComponentONE/src/fileA.c",
  "file": "C:/Project1/Root/software/ComponentONE/src/fileA.c"
},

才能让它工作。显然，现在还有其他问题，比如

error: unknown argument: '-fstrict-volatile-bitfields' [clang-diagnostic-error]

但这是因为选项-fstrict-volatile-bitfields只存在于gcc，而存在于clang。我会说问题解决了。