on master help sign in
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.

commit93e6eac15a1302aa790fec2778cdfee3eefd94e3 authorMichael Davis <mcarsondavis@gmail.com> dateSat 28 May 2022, 21:06 (4 years ago) parent7706a4a
1 file changed+3−1
helix-loader/src/grammar.rs+3−1
helix-loader/src/grammar.rs+3−1
@@ -355,7 +355,9 @@ fn build_tree_sitter_library(src_path: &Path, grammar: GrammarConfiguration) ->
355355 }
356356 }
357357
358− let output = command.output().context("Failed to execute C compiler")?;
358+ let output = command
359+ .output()
360+ .context("Failed to execute C/C++ compiler")?;
359361 if !output.status.success() {
360362 return Err(anyhow!(
361363 "Parser compilation failed.\nStdout: {}\nStderr: {}",