This page lists the C++ libraries, frameworks and build tools Niro was tested against, and whether it recognised each one.

What the marks mean.

The test code is made up for the purpose: one small service per library, with the names invented. So "supported" means Niro recognised it there. It is good evidence, but it is not a promise about every codebase. If Niro misses something in your code, the coverage audit reports the gap on its own (see Coverage audit).

Web frameworks and HTTP servers (the routes your code serves)

3 supported, 2 partly, 10 not yet.

Name Status Ways of using it that were tested
Boost.Beast not yet no: one handler comparing req.method() and req.target()
civetweb C++ (CivetServer) not yet no: server.addHandler(path, handler) with CivetHandler::handleGet/handlePost
cpp-httplib supported yes: svr.Get(path, lambda)
yes: svr.Post(path, named_function)
yes: regex path in a raw string literal
yes: path parameter written :id (cpp-httplib 0.10+)
cpprestsdk (Casablanca) not yet no: http_listener(U("http://host:port/path")) + listener.support(methods::GET, h)
Crow supported yes: CROW_ROUTE(app, path)(handler), GET by default
yes: .methods("POST"_method)
yes: .methods(crow::HTTPMethod::Delete)
yes: crow::Blueprint bp(prefix) + CROW_BP_ROUTE(bp, path)
yes: CROW_WEBSOCKET_ROUTE(app, path)
yes: CROW_CATCHALL_ROUTE(app)
yes: app.route_dynamic(path)(handler)
Drogon partly yes: app().registerHandler(path, handler, {Get})
yes: registerHandler(path, handler, {drogon::Post, drogon::Put})
no: HttpController<T> with METHOD_LIST_BEGIN, ADD_METHOD_TO (absolute) and METHOD_ADD (relative to /ns/Class)
no: HttpSimpleController<T> with PATH_ADD(path, verbs)
partly: WebSocketController<T> with WS_PATH_ADD(path)
Oat++ not yet no: ENDPOINT("VERB", "/path", name, params...) inside an ApiController
Pistache supported yes: Routes::Get(router, path, Routes::bind(&C::m, this))
POCO Net not yet no: HTTPRequestHandlerFactory::createRequestHandler comparing request.getURI()
Qt HTTP Server not yet no: QHttpServer::route(path, QHttpServerRequest::Method::X, h)
RESTinio not yet no: router->http_get(path, h), http_post, http_put, http_delete
Seastar httpd not yet no: routes.add(operation_type::GET, url("/x"), handler)
userver not yet no: HttpHandlerBase subclass; path in static_config.yaml (path: /v1/orders)
uWebSockets partly partly: uWS::App().get(path, h).post(...).del(...).ws<T>(path, ...)
Wt not yet no: WServer::addResource(&resource, path)

The language's own HTTP server

0 supported, 0 partly, 2 not yet.

Name Status Ways of using it that were tested
Boost.Asio (raw TCP) not yet no: acceptor + read_until("\r\n\r\n") + hand-parsed request line
POSIX sockets (no library) not yet no: accept + recv, request line split with istringstream, compared with ==

HTTP client libraries (the calls your code makes to other services)

1 supported, 0 partly, 10 not yet.

Name Status Ways of using it that were tested
Boost.Beast not yet no: resolver.resolve(host, port) + http::request<...>{http::verb::get, target, 11}
cpp-httplib not yet no: httplib::Client cli(base or host, port); cli.Get(path), Post, Delete
cpprestsdk (Casablanca) not yet no: http_client(U(base)).request(methods::GET, U(path))
cpr not yet no: cpr::Get(cpr::Url{literal})
no: cpr::Post(cpr::Url{...}, cpr::Body{...}, cpr::Header{...})
no: cpr::Session; session.SetUrl(cpr::Url{...}); session.Get()
no: cpr::Url{std::string(std::getenv("X")) + "/path"}
curlpp / cpp-netlib not yet no: curlpp::options::Url(url); boost::network::http::client::request(url)
Drogon not yet no: HttpClient::newHttpClient(base); req->setPath(p); req->setMethod(drogon::Get); client->sendRequest(req)
libcurl not yet no: curl_easy_setopt(h, CURLOPT_URL, literal) from C++
Oat++ not yet no: ApiClient with API_CALL("VERB", "/path", name)
POCO Net not yet no: HTTPClientSession(host, port) + HTTPRequest(HTTP_GET, path) + sendRequest
Qt Network not yet no: QNetworkAccessManager::get / post / deleteResource(QNetworkRequest(QUrl(url)))
restclient-cpp supported yes: RestClient::get(url), post(url, type, body)

The language's own HTTP client

0 supported, 0 partly, 2 not yet.

Name Status Ways of using it that were tested
POSIX sockets (no library) not yet no: getaddrinfo + connect + send of a request line
WinHTTP (Windows built-in) not yet no: WinHttpConnect(session, host, port) + WinHttpOpenRequest(conn, verb, path)

gRPC

0 supported, 1 partly, 1 not yet.

Name Status Ways of using it that were tested
Apache bRPC not yet no: protobuf service implemented by a class, server.AddService(&impl, ...)
gRPC C++ partly yes: class X : public pkg::S::Service with override methods (grpc-plan.md section 3 (cpp row) and 8.1)
yes: override taking ServerWriter<T>* / ServerReader<T>* / ServerReaderWriter<A,B>*
yes: S::AsyncService member; service_.RequestM(&ctx, &req, &responder, cq, cq, tag)
yes: class X : public S::CallbackService with reactor overrides (incl. bidi)
partly: auto stub = S::NewStub(channel); stub->M(&ctx, req, &reply)
yes: stub->AsyncM(...) and stub->PrepareAsyncM(...) (prefix stripped)
yes: stub->async()->M(&ctx, &req, &reply, callback)
yes: std::unique_ptr<ClientReader<T>> reader(stub->M(&ctx, req))
yes: grpc::CreateChannel(std::getenv("X"), creds) feeding NewStub
yes: grpc::GenericStub::PrepareUnaryCall(&ctx, "/pkg.S/M", buf, &cq)
no: AsyncGenericService / CallbackGenericService (method chosen at run time)

Databases and data stores

0 supported, 1 partly, 14 not yet.

Name Status Ways of using it that were tested
AWS SDK for C++ (DynamoDB) not yet no: PutItemRequest req; req.SetTableName(name); client.PutItem(req)
DataStax C/C++ driver (Cassandra, ScyllaDB) not yet no: cass_statement_new(cql, n) + cass_session_execute
Drogon ORM not yet no: db->execSqlAsync(sql, ok, err, args...)
no: db->execSqlSync(sql, args...)
no: orm::Mapper<Model>(db).findAll() (table from the generated model)
hiredis (from C++) not yet no: redisCommand(ctx.get(), "SET key %s", ...) in a .cpp file
libpqxx partly partly: tx.exec(sql)
no: tx.exec_params(sql, args...)
no: tx.query<T...>(sql) (libpqxx 7.8+)
yes: tx.query_value<T>(sql)
yes: tx.query1<T>(sql)
no: c.prepare(name, sql) then tx.exec_prepared(name, args)
no: pqxx::connection c{uri}
MongoDB C++ driver (mongocxx) not yet no: db.collection(name).insert_one / find_one
no: auto coll = db["ratings"]; coll.update_one(...)
no: collection(name).aggregate(pipeline)
MySQL Connector/C++ (JDBC API) not yet no: stmt->executeQuery(sql)
no: con->prepareStatement(sql) + executeUpdate
no: stmt->execute(sql)
MySQL Connector/C++ (X DevAPI) not yet no: sess.getSchema(db).getTable(name).select(...) / getCollection(name).add(...)
ODB / sqlpp11 not yet no: typed ORMs (db->persist(obj), select(...).from(tab))
POCO Data not yet no: session << "SQL", into(x), use(y), now
Qt SQL not yet no: QSqlQuery::exec(sql) and prepare(sql) + exec()
redis-plus-plus not yet no: redis.set(key, v), get(key), del(key)
no: redis.hset(key, field, v), hget(key, field)
no: redis.command<T>("VERB", key, ...)
SOCI not yet no: sql << "SELECT ...", soci::use(x), soci::into(y)
no: soci::statement st = (sql.prepare << "...", use(...)); st.execute(true)
no: soci::rowset<soci::row> rs = (sql.prepare << "SELECT ...")
sqlite_orm not yet no: make_storage(file, make_table(name, columns...)); storage.get_all<T>()
SQLiteC++ not yet no: SQLite::Database::exec(sql)
no: SQLite::Statement query(db, sql)

Messaging and events (queues, topics, streams)

0 supported, 0 partly, 9 not yet.

Name Status Ways of using it that were tested
AMQP-CPP (Copernica) not yet no: channel.publish(exchange, routing_key, body)
no: channel.consume(queue).onReceived(cb)
no: declareExchange / declareQueue / bindQueue(exchange, queue, key)
AWS SDK for C++ (SQS) not yet no: SendMessageRequest.SetQueueUrl(url) + sqs.SendMessage; ReceiveMessageRequest
cppkafka not yet no: producer.produce(MessageBuilder(topic).partition(p).payload(x))
no: BufferedProducer.add_message(make_builder(topic)...)
no: consumer.subscribe({topics}); consumer.poll()
cppzmq not yet no: zmq::socket_t s(ctx, zmq::socket_type::pub); s.bind(addr); s.send(...)
no: s.connect(addr); s.set(zmq::sockopt::subscribe, prefix)
no: zmq::socket_type::rep bound; recv then send
Eclipse Paho MQTT C++ not yet no: cli.publish(topic, payload, qos, retained)
no: mqtt::make_message(topic, payload) then cli.publish(msg)
no: cli.subscribe(topic, qos); consume_message()
no: mqtt::topic t(cli, name, qos); t.publish(payload)
no: mqtt::client (synchronous) publish(make_message(...))
librdkafka C++ API not yet no: producer->produce(topic_name, partition, flags, payload, len, ...)
no: RdKafka::Topic::create(producer, name, conf, err) then produce(topic, ...)
no: KafkaConsumer::create + consumer->subscribe({topics})
NATS C client (from C++) not yet no: natsConnection_PublishString / Subscribe called from C++
redis-plus-plus not yet no: redis.publish(channel, message)
no: auto sub = redis.subscriber(); sub.subscribe(channel); sub.consume()
SimpleAmqpClient not yet no: ch->BasicPublish(exchange, routing_key, BasicMessage::Create(body))
no: ch->DeclareQueue(q); ch->BasicConsume(q); BasicConsumeMessage(tag)

Build tools and package managers

14 supported, 0 partly, 0 not yet.

Name Status Ways of using it that were tested
Bazel (Bzlmod) supported yes: MODULE.bazel + BUILD.bazel with cc_binary / cc_library / cc_test; bazel-out and bazel-bin output
Bazel (WORKSPACE) supported yes: WORKSPACE + BUILD files (pre-Bzlmod)
CMake supported yes: root aggregator + add_subdirectory; add_library and two add_executable; target_link_libraries
CMake FetchContent supported yes: FetchContent_Declare + MakeAvailable; fetched sources under build/_deps
CMake presets supported yes: CMakePresets.json with binaryDir out/build/<preset> (Visual Studio and VS Code default)
Conan (conanfile.txt) supported yes: conanfile.txt [requires] / [generators] over a CMake tree
Conan 2 (conanfile.py) supported yes: conanfile.py with cmake_layout over a CMake tree; generators under build/<cfg>/generators
GN + Ninja supported yes: BUILD.gn with executable() / static_library(); .gn root; out/<dir> output
Meson with wraps supported yes: meson.build subdir() tree; subprojects/*.wrap and downloaded sources; builddir/
MSBuild (Visual Studio .sln + .vcxproj) supported yes: .sln listing .vcxproj files; ConfigurationType Application / StaticLibrary; ProjectReference; x64/Release output
Premake 5 supported yes: one premake5.lua at the root with project blocks, kind ConsoleApp / StaticLib
qmake (Qt) supported yes: TEMPLATE = subdirs root, TEMPLATE = app and TEMPLATE = lib .pro files
vcpkg manifest mode supported yes: vcpkg.json + vcpkg-configuration.json; packages installed in vcpkg_installed/
xmake supported yes: xmake.lua with target(), set_kind("binary" | "static" | "shared"), add_deps

Project and folder layouts

6 supported, 2 partly, 0 not yet.

Name Status Ways of using it that were tested
C library + C++ service (extern "C") supported yes: a .c library with an extern "C" guarded header called from .cpp
CMake partly yes: aggregators two levels deep: services/orders/{core,api}, libs/pricing
yes: one root CMakeLists declaring a library and two executables over src/<target>/
yes: examples/ and benchmarks/ executables declared EXCLUDE_FROM_ALL
yes: add_executable(... IMPORTED) for a tool, add_library(Shop::pricing ALIAS pricing)
yes: add_library(x INTERFACE) header-only and add_library(y OBJECT)
partly: two programs whose main functions are byte-identical, no namespace
CMake + GoogleTest / Catch2 supported yes: test folders whose add_executable is registered with gtest_discover_tests or add_test
header-only library supported yes: a library with only include/<name>/*.hpp and an INTERFACE target
include/ + src/ + apps/ (Pitchfork-style) supported yes: public headers include/<proj>/, implementation src/, binaries apps/<name>/
native addon inside a Node package (node-gyp / cmake-js) supported yes: binding.gyp and a CMakeLists under a package.json
protoc output checked in partly partly: proto/gen/*.pb.cc, *.grpc.pb.cc next to the .proto files
vendored and submodule dependencies supported yes: third_party/, external/ (git submodule), extern/ copies of public libraries