Vivado Tool: Allow for "none" option for synth#505
Merged
olofk merged 2 commits intoolofk:mainfrom Mar 31, 2026
Merged
Conversation
ArkoshEternal
changed the title
Owner
|
This makes sense. Please fix the formatting (I recommend using presubmit first and I'm happy to merge. |
Contributor
Author
|
Done! Apologies, forgot to pre-commit install on that checkout |
Owner
|
Great! Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vivado Tool: Enable post_build scripts to run if synth == none is selected
Summary
Reasoning
The vivado tool currently fails to run any of the post_build scripts if synth is set to none. This allows custom user injection of post_build scripts which can run custom tcls, etc. to allow a broader use of vivado features while still leveraging project mode through fusesoc's project make target.