CSV File Output

[NJDFan]

Just ran into another situation where it would be handy to be able to cook a sequence of .pro files down into a .csv file that just provides a listing of which files get compiled into which library; this time for the Sigasi VSCode plugin.

The simple way to do this seems like it would be to just to create a new set of VendorScripts_ for which analyze_* outputs lines to the CSV and everything else is just stubbed out. I'd be happy to write that up myself and send in a PR for it, but just a quick question.

Right now, VendorScript_Reports.tcl basically is that, just a set of stub-outs. Would it be better to implement this into Reports, or into a new VendorScript_CSVfile.tcl? My inclination is the former, just so that there's not one more file in the world, but I'm happy to do it however the project wants it done.

Either way, my envisioned use case winds up as something like either

#!/usr/bin/env tclsh
set ::env(OSVVM_TOOL) Reports
set ::env(CSVFILE) ../projectfiles.csv
source ../OSVVM/Scripts/StartUp.tcl
build toplevel.pro

or

#!/bin/sh
OSVVM_TOOL=Reports CSVFILE=../projectfiles.csv tclsh << EOF
source ../OSVVM/Scripts/StartUp.tcl
build toplevel.pro
EOF

[JimLewis]

Hi Rob,
A good starting point is VendorScripts_CompileList.tcl which for each library creates a list of files associated with it. For some tools it may need a file normalize on the file name to get it into the correct directory.

If Sigassi needs something specific, it would be pretty easy to update this file.

Best Regards,
Jim

[JimLewis]

It would not be unreasonable to have a Sigassi specific one. It is a good example. Similar things should be able to generate FPGA project files - for Xilinx, Altera, ...