cpr VS daw_json_link

This one might fit the bill https://github.com/libcpr/cpr

cmake_minimum_required(VERSION 3.15) project(xrpc++ DESCRIPTION "C++ AT Protocol XRPC library" VERSION 1.0.0 LANGUAGES CXX) include(FetchContent) FetchContent_Declare(cpr GIT_REPOSITORY https://github.com/libcpr/cpr.git GIT_TAG 2553fc41450301cd09a9271c8d2c3e0cf3546b73) # The commit hash for 1.10.x. Replace with the latest from: https://github.com/libcpr/cpr/releases FetchContent_MakeAvailable(cpr) FetchContent_Declare(json URL https://github.com/nlohmann/json/releases/download/v3.11.2/json.tar.xz) FetchContent_MakeAvailable(json) add_library(${PROJECT_NAME} SHARED src/lexicon.cpp src/xrpc.cpp ) target_link_libraries(${PROJECT_NAME} PRIVATE cpr::cpr) target_link_libraries(${PROJECT_NAME} PRIVATE nlohmann_json::nlohmann_json) set_target_properties(${PROJECT_NAME} PROPERTIES VERSION ${PROJECT_VERSION}) set_target_properties(${PROJECT_NAME} PROPERTIES SOVERSION 1) target_include_directories(${PROJECT_NAME} PUBLIC include) set(CMAKE_BUILD_TYPE debug)

include(FetchContent) FetchContent_Declare(cpr GIT_REPOSITORY https://github.com/libcpr/cpr.git GIT_TAG 2553fc41450301cd09a9271c8d2c3e0cf3546b73) # The commit hash for 1.10.x. Replace with the latest from: https://github.com/libcpr/cpr/releases FetchContent_MakeAvailable(cpr)

There is also the cpr package which should offer a more c++ focussed interface for curl.

So I'm very new to C++ and I'm trying to write a C++ version of a tool that I put together in Python. I'm trying to use libcpr for all my HTTP needs. I've spent the day trying to get it set up and working, but I'm getting a bunch of linking errors when I try to run. I really don't know if I did the building of it correctly, I'm trying to use Visual Studio Community 2022 and the Usage section of their docs talks about CMake and a couple package manager methods.

I think vcpkg manifests have solved a really key portion of the "please give me these libraries" problem. Couple lines in a json file, pass CMake to your vcpkg toolchain script path and triplet, and you're pretty much done with dependencies. I actually used it for a project with libcpr/cpr and a couple other popular libraries, and I was shocked at how painless it was to get up and running with some web request stuff.

Libraries like nlohmann's json, cpr, fmt are prime examples of what I'm seeking. Any suggestions?

Basically specifying the language and the repo, and it does work when the request is made from postman or from the browser. However, when using https://github.com/libcpr/cpr, I'm getting the following response:

They might have good luck with https://github.com/beached/daw_json_link it has support for stuff like JSON lines and alike plus other ways that only use as much ram as their underlying data structures do as it parses directly to the user DS. Plus it has an iterator/range interface for things like arrays if needed.

We will add more benchmarks in the future, but for now you can see the comparison of daw_json_link with rapidjson. glaze is faster than daw_json_link, which is over twice as fast as rapidjson.

I am biased, but prefer https://github.com/beached/daw_json_link Super fast and you work with your native data structures without the overhead of DOM parsing/lookup

You can also look into https://github.com/beached/daw_json_link which claims to support nullable values in the readme.

The library I author does this. https://github.com/beached/daw_json_link . It's fast, GB/s too, and provides the mapping mechanism, iteration types, json lines support, event based parser, along with a non-owning json_value for when the mappings don't fit right or if one is querying. Pretty much everything but an owning JSON value as it's not something I've ever needed more than temporarily and brings a lot of complexity that is solved by using the actual C++ data structures one is eventually parsing into anyways.

So DAW JSON Link does have a DOM view, however it does not have a owning view. The json_value(even supports JSON Path in a limited form) type and json_raw mappings can help here. But there is no hard line between parsing view the json_value and the mappings to concrete data structures. One can mix and match.

Is this the repo? Never saw it linked in our convo, and I’d like to give it a whirl.

daw_json_link is what you're looking for : https://github.com/beached/daw_json_link

Check out https://github.com/beached/daw_json_link , it provides a non-typeerased way to parse JSON straight into user-defined data structures.