On 22 Jun 2025 14:27, Leonid . via Boost wrote:

Hello, guys. I'm Leonid and I want to propose my C++ library for Boost. Currently, I develop one and don't use VCS by now. In future I would prefer use SVN instead of Git. Is it possible for Boost library?

There are examples when libraries are maintained externally, and then periodically merged into the Boost version of the library, which gets released as part of Boost. You could maintain your library externally in SVN, but you would still have to merge your changes into the Boost version that would still be in git (specifically, on GitHub). IMHO, merging changes from SVN to git is much more difficult than between git repositories, so I'm not sure it is worth the trouble. Is there any particular reason why you want to use SVN?

Also I want to ask why I should setup CMake for header only library? (In doc you wrote "Required for all libraries.")

CMake (and, now, Boost.Build) are mandatory for all Boost libraries in order to express dependencies between libraries and their include paths, as well as any other requirements, such as defines and C++ version. For compiled libraries, the build systems are also used to compile the library.

пн, 23 июн. 2025 г. в 12:30, Leonid . via Boost <boost@lists.boost.org>:

Also I want to ask why I should setup CMake for header only library? (In doc you wrote "Required for all libraries.")

One function that a build system performs for header-only libraries is running tests and building documentation and examples. It would be simpler for your potential contributors to just use a build system rather than to figure out your custom way of doing things. Specifically for documentation you have the option to just store pre-built HTML pages, but that has its downsides. Note that without tests your chance of getting accepted approaches zero. And by having a custom system to run tests you reduce the likelihood of getting reviews, which also reduces the chance of getting accepted.