Jim Porter

Closing based on the above comment.

Yeah, this is a goal for 2.0, but there are some subtleties I haven't quite worked out, like what to do when the directory structure has changed between versions. In...

I'm not actually sure. It probably does? (I've never used Gitlab, so I don't know much about how its pages work.) At worst, you could manually generate the docs and...

Hmm. Unfortunately, Gitlab isn't my area of expertise, so I'm not sure I can be much help. If anyone else out there knows how to get this working on Gitlab...

This sounds like it would be pretty trivial to implement as a parameterization on expectations. I'm not sure it's something I'd want in mettle proper (it's bad enough that I...

`caliber` is still a demonstration, so its "docs" are just the `test` folder in the repo. I hope to get back to working on that later this year though... As...

Sorry, but no. The reason I made mettle's current build system (bfg9000) in the first place is because I dislike CMake enough that I'd rather write my own build system...

I filed #43 to track making a Debian package. I'm most of the way done, and if you want to live on the bleeding edge, you can try using mettle...

Reopening this. I think there's probably some value in a *minimal* CMakeLists.txt. I don't want it to support everything that build.bfg does since that'd just be more maintenance burden, but...

@JohnGalbraith Do you mind if I adapt your `CMakeLists.txt` to include in this repo? It looks like you've already worked out most of the issues, so it seems a waste...