Have at least one release of the code with a pre-compiled binary about clang-unformat HOT 5 OPEN

Definitely.

I usually maintain these semver version tags properly in other projects (such as [1] and [2]).

The only reason I didn't do that here is I didn't have high hopes for this project. I just shared it to get some feedback at first.

Maintaining proper version tags is easy. Providing pre-compiled binaries is a little more complex. Vcpkg can easily take care of boost and fmt without changing anything in CMakeLists.txt though.

from clang-unformat.

You can also find_package(futures QUIET). The library can be installed and has a CMake config script. It doesn't exist in any package manager though. The packages are only available in the original repo. It's not in version 1.0.0 yet.

from clang-unformat.

I'm planning to package it for the Nixpkgs package collection, which would allow it to be used on supported platforms such as Linux and Mac OS. However, it's encouraged to reference a tagged revision instead of chasing behind the master branch. AFAIK, many packaging projects also expect / require an official version tag from the upstream.

It would be great for this excellent project to have git tags representing the version. A release can be added onto a git version tag.

2.6 Git Basics - Tagging | Git Book
https://git-scm.com/book/en/v2/Git-Basics-Tagging

About releases | GitHub Doc
https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases

from clang-unformat.

Since only boost doesn't have a FetchContent alternative in CMakeLists.txt, we could use https://github.com/alandefreitas/FetchBoostContent to provide that alternative. In this case, the user wouldn't need any of the dependencies available to compile the application.

from clang-unformat.

@alandefreitas On the other hand, how do I manually specify the libraries (such as futures) to use instead of fetching them?

Nixpkgs, and RPM doesn't allow arbitrary internet access during build, and it would be very helpful to have the fetch-free build instruction included in the README.

from clang-unformat.