-
Notifications
You must be signed in to change notification settings - Fork 48
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
Relative paths in flow configurations are handled in respect to CWD instead of file location. #640
Comments
can you give me suggestions how can i contribute on this |
@suksham11 Hi, thanks for your interest in this project.
If you found the terminology here a bit confusing, the "Fundamental concepts" section of docs might be helpful. Be sure to also check developer notes Handling it just for dependencies provided by the user should be a good starting point and a valuable contribution on its own. 1) is out of reach as for now and so is the "value" part of 2). The reason why values are a problem is because they are untyped, so we don't know whether they are a path or not - it's up to a module to decide how to parse a value. I would love to see it change as it would greatly improve error reporting, but it's easier said than done. An alternative approach, one I'd like a bit more would be to allow dependencies to be specified in platform definitions. In that case we would probably want to exclude them from modification tracking mechanism ( There are places in the in which |
First described in #554
This behviour forces the user to run f4pga with PWD being equal to the location of flow.json. Otherwise, the paths in flow.json would be resolved incorrectly.
The text was updated successfully, but these errors were encountered: