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

discussion on cIncludeDir, cCompile, cImport #7

Closed
timotheecour opened this issue Nov 22, 2018 · 0 comments
Closed

discussion on cIncludeDir, cCompile, cImport #7

timotheecour opened this issue Nov 22, 2018 · 0 comments

Comments

@timotheecour
Copy link
Contributor

timotheecour commented Nov 22, 2018

i think cIncludeDir("include”) is being mis-used; IMO cCompile and cImport should be given actual paths where sources (h and c) live, and cIncludeDir would only be used to resolve where to find bar.h if a h or c file contains #include bar.h

Note: further discussed here: https://gitter.im/nimgen/Lobby?at=5bf5f541a115c91ef77149b9

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