06-29-2015 04:42 PM - edited 06-29-2015 04:43 PM
Other than redirecting to a NUL device, is there an easy way to tell Vivado to only log to the journal file, but not write to the console?
With even fairly small builds the synthesis output to the console seems to be using a lot of time.
This is for non-project mode run from a command shell. The -mode switch is set to batch.
Win7 x64, Vivado 2015.1.
06-30-2015 01:10 AM
06-30-2015 02:24 PM - edited 06-30-2015 02:24 PM
Thank you for the reply, muzaffer. But, the -mode tcl seems to only differ from -mode batch in that it does not exit Vivado after it completes script execution (UG835 (v2015.1), p.4). It still logs lots of output to the console.
06-30-2015 05:08 PM
06-30-2015 07:58 PM
I tried -notrace after the -source <file> command to Vivado. I could not find any documentation on a -notrace switch to Vivado itself.
This did seem to source the file with the -notrace option to source.
That reduced the output slightly, but the main culprit for massive output is synthesis and implementation information. And that still comes out both in the log file as well as to the screen.
I did, based on what I found while looking for the -notrace option you suggested, find a backwards workaround, though I do not love it: I use -nolog and -nojournal and then redirect the console output into a log file.
This is backwards I turn off the log, and keep the console output, but at least Vivado is not writing to two places.
I still would like a simple way to tell Vivado to just show serious errors to the console and only write the bulk output to the log and journal.