Fabian Sauter

I'd say there is something wrong with your tool chain file. As far as I'm aware `.dylib` is MacOS and `.so` is linux. @KingKili Do you know anything about this?

Well I don't think this is a cpr issue then and more a general build system issue where you do not target the correct system.

Although I never developed for Android or iOS this is probably something like it can't find the libs. Let me know when you get it up and running, so we...

It would be awesome if someone could create a PR for the https://github.com/libcpr/docs repo with a more detailed summary/run through description for this.

In my eyes this is not correct. Perhaps there is something wrong in curl. Did you already try to build libcurl without cpr?

Thanks for taking the time to note down your steps! I will try to move them inside the docs.

@cpsauer since you are working on Bazel rules anyway please let me know when you are done, so I can have a look at the required changes. The issue here...

Oh, sorry overlooked that one. I can have a look at it next week. I also think I know why this is happening. This is probably connected to the warnings...

My plan is to make use of `C++17` features like [`std::opt`](https://en.cppreference.com/w/cpp/utility/optional) and the new default deleter for [`std::unique_ptr`](https://de.cppreference.com/w/cpp/memory/unique_ptr) and [`std::shared_ptr`](https://de.cppreference.com/w/cpp/memory/shared_ptr). Besides that create a better [RAII](https://en.cppreference.com/w/cpp/language/raii) wrapper for curl sessions...

> Also being able to pass `string_view` into `cpr::Url` and other applicable locations would also be nice Yes, good idea!