-
Notifications
You must be signed in to change notification settings - Fork 75
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
make generate-tests fails for earlgrey out of the box #913
Comments
Using a scratch area is a good idea (I guess we will have to use virtualenv for that), but I think that expanding the README is a good first step - the fusesoc dependency is included in our requirements.txt too (and that's what the CI currently uses). |
hzeller
referenced
this issue
in hzeller/sv-tests
Jul 10, 2020
Issue #913 Signed-off-by: Henner Zeller <[email protected]>
hzeller
added a commit
that referenced
this issue
Jul 11, 2020
Issue #913 Signed-off-by: Henner Zeller <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On a default install with all the dependencies installed mentioned in the README,
make generate-tests
will fail, specifically:Reason is, that there are a few requirements that need to be installed; after doing that with
The above
make generate-earlgrey
call works without errors.Getting these requirements should be part of the
./generators/earlgrey
script. Is it possible for the script to install these dependencies locally in a scratch area without messing with the users'~/.local
?I leave it up to the Python experts how to solve this best.
The text was updated successfully, but these errors were encountered: