Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for out-of-tree tools #414

Open
jgoeders opened this issue Dec 17, 2023 · 0 comments
Open

Support for out-of-tree tools #414

jgoeders opened this issue Dec 17, 2023 · 0 comments

Comments

@jgoeders
Copy link
Member

Currently most external tools (yosys, fasm2bels) are assumed to be a submodule. However, it would be nice if there was a way (eg environment variable) to specify another location.

With #385 install_fasm2bels will look for the environment variable BFASST_PATH_FASM2BELS and install fasm2bels there if it is not already installed. However, this is primarily used as a caching mechanism for the CI and has some potentially unwanted behavior when run locally. It currently looks in the BFASST_PATH_FASM2BELS directory for a fasm2bels_commit.txt file with the contents containing a commit hash. If the file does not exist with the expected hash contents, the entire directory is deleted and fasm2bels is re-cloned at that directory. This is fine for CI, but a bit problematic locally if the user is working on updates to the external tool (ie they have made changes to their fasm2bels copy) and then we delete it. Given this, we should improve this mechanism before documenting that it can be used for user-supplied external tools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant