-
Notifications
You must be signed in to change notification settings - Fork 268
Help wanted - adding new backend to fusesoc/edalize #738
Copy link
Copy link
Open
Description
Hello,
I am toying with fusesoc/edalize to add a new testbench linter named svck - it is built on top of Verible, but in Python. I have a hacked flow that seems to run for now, but am sure it is a hack and not clean. Here is what I have done so far:
- Read FuseSoC manual, it sort of pointed me to Edalize
- Read Edalize manual, added a new file named svck.py (copied from veriblelint, modified as per svck argument/req)
- Now, honestly I didn't read/search long enough to see how to use my modified/updated edalize with fusesoc - so that would be my basic Q (see below). For now I copied the svck.py to .lcoal/lib/.. and got it working
My questions/help requests:
- Is there a unified doc for addressing new tool addition - or what I did above in 1,2 is the right approach?
- How to use my modified/updated edalize with fusesoc?
Thanks
Srini
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels