Describe the bug
sometimes $#it happenes, and console has following text:
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the E:!Projects\Embedded!Eclipse-WS\ESP32-Blink-fucking\build\log\idf_py_stderr_output_7588 and E:!Projects\Embedded!Eclipse-WS\ESP32-Blink-fucking\build\log\idf_py_stdout_output_7588
so, user have to open the output files and find himself the error message.
it sucks, since another plugins EXTRACT error messages from output files and SHOW THEM to user inside build console.
Expected behavior
Implement the IBM principle: "machines should work; people should think" - not "digg yourself into some ninja output files and find out why the huck up happened", but "we've parsed output of the command for you and it says 'XXXXXXXXXX'"
Describe the bug sometimes $#it happenes, and console has following text:
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the E:!Projects\Embedded!Eclipse-WS\ESP32-Blink-fucking\build\log\idf_py_stderr_output_7588 and E:!Projects\Embedded!Eclipse-WS\ESP32-Blink-fucking\build\log\idf_py_stdout_output_7588
so, user have to open the output files and find himself the error message. it sucks, since another plugins EXTRACT error messages from output files and SHOW THEM to user inside build console.
Expected behavior Implement the IBM principle: "machines should work; people should think" - not "digg yourself into some ninja output files and find out why the huck up happened", but "we've parsed output of the command for you and it says 'XXXXXXXXXX'"
Espressif-IDE Product Information: Operating System: windows 11 Java Runtime Version: 19+36 Eclipse Version: 4.31.100.v20240229-0520 Eclipse CDT Version: 11.5.0.202312062348 IDF Eclipse Plugin Version: 2.12.1.202402231119 ESP-IDF v5.2.1-dirty Python set for IDF_PYTHON_ENV: Python 3.9.16