Closed rnpnr closed 10 months ago
This doesn't detect changes in header files (both Vis own, and system ones).
You might want to use the -MD
or -MMD
gcc options.
I have a similar commit it in my fork - build: incremental compilation
I guess I never really bother tracking headers. I'm not really against it though. What do other people think? I've added it as a second commit for now.
PR has been merged to https://git.sr.ht/~mcepl/vis and although only the Makefile part is relevant (and I have also added https://git.sr.ht/~mcepl/vis/commit/25fe086eb427 for build.sr.ht), it seems to be building and working just fine.
I think it happened after this commit that a bunch of .d
and .o
files are generated on make
. Is it possible to avoid this as it clutters up the directory?
Is it possible to avoid this as it clutters up the directory?
Yes you are right, fixed here: 4ca7119.
fixed here: https://github.com/martanne/vis/commit/4ca711941423a9bdd206b3efb298aa9793682f10.
Oh oops I guess |
in make rules is a GNU extension so I broke building
on Open/FreeBSD (macOS uses GNU make). I will have to do a separate fix
for that.
Its been annoying me for a while that every time I change a single source file I have to rebuild all of them. Now we rebuild only the files that were touched.
This should also make the ci marginally faster since the files can be built in parallel.