Alexandre Mutel

> That's what I got from the binaries that I buil That being said, I think I checked only libktx, but looking at cmake scripts, for tools, it looks like...

I could propagate the tag to the mkversion with e.g a special argument like `--version` or something like this. Would that be enough?

> Are you working on this? Yes, I will do it on my spare time.

@MarkCallow so I have pushed a fix that propagates the version to mkversion, but it seems that there was a discrepancy between the version expected for tools (prefixed with v)...

Oh, actually, that's because a few lines later in version.cmake `KTX_VERSION_FULL` is overridden and discarding the `v`, so should it keep the original version with `v` or not? ``` set(KTX_VERSION_FULL...

I have started to open a PR on alpine with the latest fixes from this PR [here](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/69457) to give an example of how the KTX package will be prepared there.

> The name change to `KTX_GIT_VERSION_FULL` breaks the package builds in `CMakeLists.txt` because they rely on `KTX_VERSION_FULL being` set by `cmake/version.cmake`. This won't show up in CI at this point...

> It would be really nice to have an option for configuring the inlining behavior from the outside. And it would be super useful for a configuration language to remember...

> I looked into supporting my use-case but as it turns out TOML has a lot of ambiguity in it's grammar in how the same thing (like an object) can...

> It would be very nice if the dlls in your nuget package were digitally signed. > I learn about them while exploring Kirill Osenkov's MSBuildStructuredLog. His MsBuildStructuredLog application is...