diff options
| author | Michael Davis | 2022-05-29 02:06:31 +0000 |
|---|---|---|
| committer | GitHub | 2022-05-29 02:06:31 +0000 |
| commit | 93e6eac15a1302aa790fec2778cdfee3eefd94e3 (patch) | |
| tree | ba99f660dd7bb03ac675a9ba186a0276e6314f19 /helix-loader | |
| parent | 7706a4a0d8b67b943c31d0c5f7b00d357b5d838d (diff) | |
mention the C++ compiler in the grammar build failure message (#2597)
Earlier in the builder we enable C++ (`.cpp(true)`) but only mention
the C compiler in the build failure message. Some grammars that have
C++ external scanners can provoke build failures in this step if a
C++ compiler isn't installed, so mentioning it in the error message
should help out debugging.
Diffstat (limited to 'helix-loader')
| -rw-r--r-- | helix-loader/src/grammar.rs | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/helix-loader/src/grammar.rs b/helix-loader/src/grammar.rs index df88f24b..99791f26 100644 --- a/helix-loader/src/grammar.rs +++ b/helix-loader/src/grammar.rs @@ -355,7 +355,9 @@ fn build_tree_sitter_library(src_path: &Path, grammar: GrammarConfiguration) -> } } - let output = command.output().context("Failed to execute C compiler")?; + let output = command + .output() + .context("Failed to execute C/C++ compiler")?; if !output.status.success() { return Err(anyhow!( "Parser compilation failed.\nStdout: {}\nStderr: {}", |