Dependency tracking of header-only changes about ebbrt HOT 4 CLOSED

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

from ebbrt.

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.

from ebbrt.

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.

from ebbrt.

Closing this as fixed with the latest toolchain changes

from ebbrt.