cpp-httplib VS conan

Alternatives at the low to medium level of abstraction include civetweb and mongoose, which have a common ancestor. Both of these appear to be C rather than C++, but seem to be production quality and well-documented. Another C library is cpp-httplib, which is probably too low-level for me.

I use this all the time to expose an admin rest interface to my public installations.

I'm using this one: https://github.com/yhirose/cpp-httplib

Every one of these libraries uses CMake to make it easier for end users to consume their libraries. In fact your example uses CMake as well such that I can consume it the way I describe above.

# Template file for 'yuzu-mainline' pkgname=yuzu-mainline version=1295 revision=1 _cubeb_version=75d9d125ee655ef80f3bfcd97ae5a805931042b8 _sanitizers_cmake_version=aab6948fa863bc1cbe5d0850bc46b9ef02ed4c1a _dynarmic_version=bd570e093ca1d1206961296b90df65cda7de8e87 _sirit_version=d7ad93a88864bda94e282e95028f90b5784e4d20 _mbedtls_version=8c88150ca139e06aa2aae8349df8292a88148ea1 _xbyak_version=348e3e548ebac06d243e5881caec8440e249f65f _SDL_version=f17058b562c8a1090c0c996b42982721ace90903 _cpp_jwt_version=e12ef06218596b52d9b5d6e1639484866a8e7067 _cpp_httplib_version=305a7abcb9b4e9e349843c6d563212e6c1bbbf21 _Vulkan_Headers_version=00671c64ba5c488ade22ad572a0ef81d5e64c803 create_wrksrc=yes build_wrksrc=${pkgname}-mainline-0-${version} build_style=cmake configure_args="-DYUZU_CHECK_SUBMODULES=OFF -DYUZU_TESTS=OFF -DSIRIT_USE_SYSTEM_SPIRV_HEADERS=ON" hostmakedepends="pkg-config qt5-host-tools qt5-qmake clang" makedepends="fmt-devel libenet-devel inih-devel libusb-devel liblz4-devel opus-devel zlib-devel libzstd-devel boost-devel qt5-devel qt5-multimedia-devel libva-devel ffmpeg-devel glslang-devel SPIRV-Headers catch2 json-c++ speexdsp-devel" short_desc="Nintendo Switch Emulator" maintainer="Owen Law " license="GPL-3.0-or-later" homepage="https://github.com/yuzu-emu/yuzu-mainline" changelog="${homepage}/releases/tag/mainline-0-${version}" distfiles="${homepage}/archive/refs/tags/mainline-0-${version}.tar.gz https://github.com/herumi/xbyak/archive/${_xbyak_version}.tar.gz https://github.com/MerryMage/dynarmic/archive/${_dynarmic_version}.tar.gz https://github.com/yuzu-emu/mbedtls/archive/${_mbedtls_version}.tar.gz https://github.com/mozilla/cubeb/archive/${_cubeb_version}.tar.gz https://github.com/arsenm/sanitizers-cmake/archive/${_sanitizers_cmake_version}.tar.gz https://github.com/yuzu-emu/sirit/archive/${_sirit_version}.tar.gz https://github.com/libsdl-org/SDL/archive/${_SDL_version}.tar.gz https://github.com/arun11299/cpp-jwt/archive/${_cpp_jwt_version}.tar.gz https://github.com/yhirose/cpp-httplib/archive/${_cpp_httplib_version}.tar.gz https://github.com/KhronosGroup/Vulkan-Headers/archive/${_Vulkan_Headers_version}.tar.gz" checksum="b8b2616a24653352b8afd145ee46eb9ead07c6ef3aff8c0ff3a6225b381b4b85 fbe54fc881cdfb0876ddc8f29f74674a311ba7ae4b774751cb1b637c043e3bae 170530852547ee2f5517b0a12e643646e51a9974414084d389a85632df7c4518 8d3553ea5c3b47789c5a1a6437f948525d0a8ce2a0897000a36b511000c6bad4 8c5b7ca55ee586a3e5e63de2d31c319045f92e949140a734846a0d69ad342e2e 9f5b073625375322236a94ce8d2d803cdedad321c91e63845f487b9ebfb2c433 6612f924d1f2b2c7cb37effcda5d78550fad276887ee8f9bc391b9ecbf9e4a64 2a149e79712027d2d8141e3233df2f6679825b6f78237db3db72bc6cfc08b845 b4cc0e1f89d3c60a4dde74baa730a90de13c5dd5155b09d8dd34cd3205a6e758 61a97686b03edffa737c396f54e48da2ff0a04c3f6859ec9e80853aea6508030 99443e30caee5d2c0019de6549cc0c7c0432214494617da445753fc46374a7c3" post_extract() { mv "xbyak-${_xbyak_version}" xbyak cp -r xbyak "${build_wrksrc}/externals" mv "dynarmic-${_dynarmic_version}" dynarmic cp -r dynarmic "${build_wrksrc}/externals" mv "mbedtls-${_mbedtls_version}" mbedtls cp -r mbedtls "${build_wrksrc}/externals" mv "SDL-${_SDL_version}" SDL cp -r SDL "${build_wrksrc}/externals" mv "cubeb-${_cubeb_version}" cubeb mv "sanitizers-cmake-${_sanitizers_cmake_version}" sanitizers-cmake cp -r sanitizers-cmake cubeb/cmake cp -r cubeb "${build_wrksrc}/externals" mv "sirit-${_sirit_version}" sirit cp -r sirit "${build_wrksrc}/externals" mv cpp-jwt-${_cpp_jwt_version} cpp-jwt cp -r cpp-jwt ${build_wrksrc}/externals mv cpp-httplib-${_cpp_httplib_version} cpp-httplib cp -r cpp-httplib ${build_wrksrc}/externals mv Vulkan-Headers-${_Vulkan_Headers_version} Vulkan-Headers cp -r Vulkan-Headers ${build_wrksrc}/externals }

Through development I've been making requests to my locally hosted sever using cpphttplib via HTTP and always had the intention of using HTTPS once my website was live. Not the smartest idea to leave this until the end, I know.

Have you tried searching the internet? https://github.com/yhirose/cpp-httplib

I'm new to C++, and have been trying to make a simple HTTP request. I stumbled on cpp-httplib and decided to try it out.

Conan is a package manager for C/C++. See: https://conan.io/.

The way it works is that you can provide "recipes", which are Python scripts, that automate the process of collecting source code (usually from a remote Git repository, or a remote source tarball), patching it, making its dependencies and transitive dependencies available, building for specific platform and architecture (via any number of build systems), then packaging up and serving binaries. There's a lot of complexity involved.

Here are the two recipes I mentioned:

libcurl: https://github.com/conan-io/conan-center-index/blob/master/r...

OpenSSL v3: https://github.com/conan-io/conan-center-index/blob/master/r...

Now, for the sake of this thread I want to highlight three things here:

- Conan recipes are usually made by people unaffiliated with the libraries they're packaging;

- The recipes are fully Turing-complete, do a lot of work, have their own bugs - therefore they should really be treated as software comonents themselves, for the purpose of OSS clearing/supply chain verification, except as far as I know, nobody does it;

- The recipes can, and do, patch source code and build scripts. There's supporting infrastruture for this built into Conan, and of course one can also do it by brute-force search and replace. See e.g. ZLib recipe that does it both at the same time:

https://github.com/conan-io/conan-center-index/blob/7b0ac710... -- `_patch_sources` does both direct search-and-replace in source files, and applies the patches from https://github.com/conan-io/conan-center-index/tree/master/r....

Now, good luck keeping track of what's going on there.

There were various approaches recommended depending on our language and ecosystem. My classmates who developed using Node.js were recommended npm, and PyPI or poetry for Python. Since my program is written in C++, I was recommended to look into one of vcpkg or conan, but I ultimately did not use either package manager.

Hi u/instinkt900, Conan maintainer here. Thanks for your feedback! Please remember that we actively monitor and respond to our issue tracker on GitHub (https://github.com/conan-io/conan/issues/new/choose), we’d love to hear about your specific use cases or pain points, so that we can improve your experience and that of other users. The motivation behind most of the updates in Conan 2.0 was precisely feedback from the community, and to improve our ability to continue delivering features in the constantly changing C++ ecosystem. We can certainly do this at a quicker pace, with some exciting new features recently released and in the pipeline: package metadata, transparent backup of downloaded package sources, cache least-recently-used cleanup, etc. A lot of the big decisions that we took for Conan 2.0 were taken with consensus from expert users and contributors (https://conan.io/tribe) and https://github.com/conan-io/tribe. Some specific workflows may not have 1:1 replacements in Conan 2.0, and are likely to affect some of the “less travelled roads” of Conan 1.x, including some features that were always marked as experimental. We are happy to hear feedback so that we can best satisfy these use cases. Conan 2.0 also includes a more sophisticated API to cover cases where the built-in integrations may not satisfy users needs. For what it’s worth - we have also heard very positive feedback from users about how Conan 2.0 simplifies their workflows when compared to Conan 1.x. The C++ tooling ecosystem is fragmented and moves at different speeds, including our users. So it’s always a fine balancing act, but we don’t want to leave anyone behind! An example is Conan Center - over 90% (~1200) of all recipes have been migrated to support Conan 2.0, while still maintaining compatibility with Conan 1.x, precisely to avoid breaking users that are still on Conan 1.x.

Solution: don't use git submodules - use a package manager like Conan or vcpkg.

The closest thing we have at the moment is conan[1]. It’s a cross platform package manager that attempts to implement “toolchains”, whereby different build systems can be integrated[2]. This is a big problem with package management in C/C++, there’s no single, standardised build system that most projects use. There isn’t even a standardised compiler! So when hosting your own packages using Conan, often you need to make sure you build your application for three different compilers, for three different platforms. Sometimes (for modern MacOS) also for two different architectures each.

If you control the compiler AND build system you can get away with just one package for most cases. This true for Microsoft’s C/C++ package manager, NuGet[3]

Historically, the convention has been to use the package manager of the underlying system to install packages, as there are so many different build configurations to worry about when packaging the libraries. The other advantage of using the system package manager is that dependencies (shared libraries) that are common can be shared between many applications, saving space.

[1] https://conan.io/

Anyway, the problems are today starting to get fewer, as more an more adopt standard cross-platform portable build systems, a.k.a. CMake and package managers such as vcpkg or Conan. Together this will take care of building, installing, linking and using the entire dependency tree.

Simply use a package manager: Crypto++ is available on both vcpkg and Conan.

If you want a specific version or provide a more integrated workflow that is easier to use across platforms and among many developers, use a package manager like vcpkg or Conan.

I do however always recommend using a package manager: vcpkg or Conan to install and integrate third party libraries (together with CMake). This normally solves all the typical problems with dependencies.

There's a few, look into Conan or vcpkg (the latter is my personal recommendation).