[cleversoap]

> 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.

[dasmithii]

You're correct. When fetched, modules are given their own directory and compiled locally (one directory per module/dependency). New projects are then scanned for dependencies, linked against pre-compiled libraries, and necessary headers are added to the search path.

In terms of presets, I have some [basic] defaults included myself, but more can be added in an optional config file, along with arbitrary compiler flags.

Kit is optimized for simple projects, where crazy build scripts aren't needed. So, yeah, for fine-grained control, I'd stick to existing tools. However, this may be more pleasant than alternatives for personal projects, as you mention.