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

What about .3d files in different directories? #50

Open
tahina-pro opened this issue Mar 5, 2021 · 0 comments
Open

What about .3d files in different directories? #50

tahina-pro opened this issue Mar 5, 2021 · 0 comments
Labels
3d The 3d dependent data description language and frontend

Comments

@tahina-pro
Copy link
Member

tahina-pro commented Mar 5, 2021

#41 introduced module dependency analysis assuming that all .3d files are in the same directory. In #45, I heavily rely on this assumption when generating Makefiles by prefixing all source .3d files with the same EVERPARSE_INPUT_DIR variable.

However, as far as I understand, no guard has been implemented to explicitly forbid the user to call 3d --makefile (or 3d --batch on .3d files that do depend on one another) from several directories. Should we implement such a guard? If not, should we implement anything like F*'s --include ?

@aseemr @nikswamy What do you think?

@tahina-pro tahina-pro added the 3d The 3d dependent data description language and frontend label Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3d The 3d dependent data description language and frontend
Projects
None yet
Development

No branches or pull requests

1 participant