-
Notifications
You must be signed in to change notification settings - Fork 17
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
Dependency tracking of header-only changes #94
Comments
I'd argue that the "right" solution is to complete lyget rid of our custom app Makefiles. Instead we should install EbbRT libraries, headers, and toolchain and just use standard build utilities |
Would this approach have any effect on the back-end build? I'm assume not. |
So the "bug" only applies to the front-end build -- changing headers on the backend will cause rebuilds based on how our makefiles work currently. But my proposed solution is to change how we deploy frontend and backend libraries/headers so that this bug would be an application's problem (and one they should solve in whatever way they see fit). For example, if we used cmake to build our apps, it would pick up changed headers, or if we had a slightly smarter makefile. |
Closing this as fixed with the latest toolchain changes |
Header-only changes do not trigger source to be re-built
The text was updated successfully, but these errors were encountered: