You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fusesoc has moved to the CAPI 2 standard for its core description files. The current core file wb2axip.core is CAPI 1 and will cause fusesoc to give an error to the end user. Recommend removing it to avoid confusion.
Future Improvement: individual fusesoc core files in the repo, if this is something you would like let me know and I'll get it done.
The text was updated successfully, but these errors were encountered:
This is one of my frustrations with FuseSOC. While I love the project's goals, and think very highly of its developer, I don't use it. This makes it difficult for me to maintain the core files used by it, as I never know when something changes, or what it needs to change to in order to keep a functionality I'm not using working. Likewise, I have no means of automatic testing to verify that the FuseSOC core's continue to work as desired.
I haven't personally had that issue in version 2 (started at 2.1 and now up to 2.3).
The documentation is frustrating to say the least. I end up reading source code to figure out how to use it. This is not acceptable.
I have added fusesoc core files for some of this repos IP in a separate repo. Essentially it uses a generator to git pull your repo so that the files are available to the core files in mine. Only issue is fusesoc finds your old core file and complains. Which is why I put in the request to delete it, since it seemed to serve no purpose at this point.
fusesoc has moved to the CAPI 2 standard for its core description files. The current core file wb2axip.core is CAPI 1 and will cause fusesoc to give an error to the end user. Recommend removing it to avoid confusion.
Future Improvement: individual fusesoc core files in the repo, if this is something you would like let me know and I'll get it done.
The text was updated successfully, but these errors were encountered: