[meta-xilinx] tools: app.tcl exits 0 regardless of build failure

[Jean-Francois Dagenais]

> On Jun 3, 2017, at 08:21, Mike Looijmans <mike.looijmans at topic.nl> wrote:
> 
> This is the case for most of Xilinx's tools too, they will return a "0" exit status even if the bitstream generation (or whatever) failed, also when the tcl script errors out, the tool still returns 0.

Yeah, fellow coworkers describe how painful this all becomes when trying to integrate Vivado in a CI pipeline... They had to resort to parsing the text output looking for specific know patterns which denote errors.

This is completely pathetic if you ask me. How hard is it to respect such a simple standardized convention which almost pre-dates dinosaures!

I know Xilinx has made tremendous efforts in user experience in 2017.1, can we expect the scripting support to be fixed sometime soon?