-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[VTA][Refactor] Introducing VTA_HW_PATH for easier migration #5163
Conversation
import os | ||
|
||
def get_vta_hw_path(): | ||
"""Get the VTA HW path.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is still better to have a default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks I've addressed them
vta/vta-hw/config/pkg_config.py
Outdated
|
||
def get_tvm_path(): | ||
"""Get the TVM path.""" | ||
TVM_PATH = os.getenv('TVM_PATH', None) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is better to have a default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I'll set one
@tmoreau89 Seems master CI is broken now. Could you please take a look? |
TVM community has voted for the
vta/vta-hw
directory migration (see #5102 for context). To make the switch easier:VTA_HW_PATH
environment variablevta-hw
repo, we're introducing theTVM_PATH
environment variable to point to TVM repovta-hw
from doxygen --vta-hw
will have it's own doxygen generated docsvta-hw
because it makes more sense to couple that with the config files.