> Kit modules are compiled libraries, while CCAN distributes source code only.

Could you expand on this? I assume pulling the source, compiling locally, and then adding the headers and libs to a project local include or link path. Is it individual directories for each dependency or do they get mixed together?

How are you handling macros? Do you have some preset defines you're passing in for different platforms?

I think it's an interesting idea and definitely has more polish than ccan. I don't know if I'd ever give up fine grained control in production but for small personal projects this would be ideal.