CLI11 VS tolc

Book: CLI11 book

The most feature-rich C++ CLI library is CLI11. Other popular choices include Boost.ProgramOptions, argparse, cxxopts and others.

CLI11 provides all the features you expect in a powerful command line parser, with a beautiful, minimal syntax and no dependencies beyond C++11. itk-wasm enhances CLI11 with a itk::wasm::Pipeline wrapper to support efficient execution in multiple Wasm contexts, scientific data structures, and lovely colorized help output 🥰.

Does anyone have feedback on the possible problems with CLI11 and comparisons to any other thing available in the wild not limited to the choices I tried before? Looks like a very well-thought out library according to its documentation: https://cliutils.github.io/CLI11/book/

I'd recommend to use CLI11. I was baffled by how much it can do.

I use https://github.com/jarro2783/cxxopts.git or https://github.com/CLIUtils/CLI11, or if boost is involved anyway, boost.program_options.

get_dependency(spdlog "https://github.com/gabime/spdlog" v1.8.5) get_dependency(CLI11 "https://github.com/CLIUtils/CLI11" v1.9.1) get_dependency(GoogleTest "https://github.com/google/googletest" master)

Maybe https://github.com/CLIUtils/CLI11? I really like this one and it looks like it supports TOML

I found https://github.com/jarro2783/cxxopts to be useful and https://github.com/CLIUtils/CLI11 to be really helpful if you need an non-trivial interface.

I love CLI11! It has been pretty easy all the way through. Used to use lyra before but since I wanted to have subgroups in Tolc I had to switch. Great job on CLI11 if the author is in the chat :)

I'm working on a project called Tolc that is generating bindings from C++ to other languages. When creating bindings to a class MyClass, it needs to be defined before any code using that class (for example a function that returns an instance of it). Therefore I needed to know in which order to define things. Honestly I just had so much fun solving this problem (using some C++20 and features) that I wrote a post so sum it all up:

Hi everyone!

Some friends and I were unhappy with how much work it was to use C++ from other languages. We were working in the optimizations industry and often had to prototype with python. Eventually, we created a tool to make it easier for C++ to talk to python (by generating pybind11). Later, javascript via WebAssembly was added as well. It's now at a point where it's very easy to just create a C++ library and use it from any of those languages without change. We're planning on slowly adding more languages as needed/requested. The next on the list are Swift and Kotlin.

It does not require any change to your existing public interface, but simply reads it and creates the bindings off of that. It should also work on Linux (Debian), MacOS, and Windows (Visual Studio). Here's a small demo if you'd like to test:

https://github.com/Tolc-Software/tolc-demo

And here are the repositories with the source code:

https://github.com/Tolc-Software/tolc - The executable

https://github.com/Tolc-Software/frontend.py - The python bindings generator

https://github.com/Tolc-Software/frontend.wasm - The WebAssembly bindings generator

https://github.com/Tolc-Software/Parser - The C++ parser

It is dual licensed with AGPL and, if someone wants, a commercial license as well.

Would be cool if someone finds it useful!

https://github.com/Tolc-Software/tolc - The executable and CMake wrappers

I’m just gonna drop this here: https://github.com/Tolc-Software/tolc