Cristian Le

> Config settings are something entirely processed by build backends. They have no meaning to plugins. Is that the reason why hatch uses [`tool.hatch.version.raw-options.*`](https://github.com/ofek/hatch-vcs#version-source-options)? Would implementing something like that be...

Would be helpful to also make it expandable. E.g. the project only defines version `1.4.2`, while `-rc1` are only defined in the git via tags. Then we could make it...

With the #197 merged, even if we do not have a `cmake` hook, at least it is possible to unify the version configuration to be determined by git tags. I...

Not yet, but maybe it's worth discussing this: - major blocker: extracting build directory from the preset Unfortunately there doesn't seem to be a cmake native way of doing so...

> Wouldn't it be possible to use the CMake file API to extract the information about the generated build system, including binary directory etc.? Unfortunately not, because the `file-api` files...

Isn't that message written at the end of it. How to deal if the build threw a `FATAL_ERROR`, e.g. it requested a generator that it did not support.

> @henryiii It's not a user-defined output. It's a CMake output that CMake prints at the end of running configuration via commandline. I'm not sure that you understood the context...

It would be good to have either individual issues for these features or have announcement posts on this issue (not just edits to the top level comment). That way we...

There seems to be more nuance to this, because even if we include the missing `\usepackage`, `myst` will still complain of `Undefined control sequence:`

One thing missing here could be to extend this beyond the `LaTeX` environment so that the html builder also renders correctly. Thing is this `imports` does not seem to be...