What steps will reproduce the problem?
1. Use a multi verilog file benchmark that employs "include"
What is the expected output? What do you see instead?
The script copies the verilog benchmark to perform the vtr flow. This results
in losing the include files for the benchmark
Any simple benchmark that has an include will trigger the issue.
Original issue reported on code.google.com by JanetChi...@gmail.com on 12 Nov 2012 at 8:11
Original issue reported on code.google.com by
JanetChi...@gmail.com
on 12 Nov 2012 at 8:11