New Post: Memory Assertion when linking against Casablanca

I've looked at the other threads and it seems that there no other way than to build a static library from source code...

So I've followed this blog post: https://katyscode.wordpress.com/2014/04/01/how-to-statically-link-the-c-rest-sdk-casablanca/ and built the static cpprestsdk library.

I've also looked at this thread https://casablanca.codeplex.com/workitem/18 and found some additional tips to make it work..

So now when I link produced lib to existing project, I was still getting few linker errors from oauth1.obj and web_utilities.obj as below. Is it related to some recent changes in the C++ REST SDK project, which were not present at the time of above posts?

So, finally, to be able to link without errors, I had to add these libraries:

winhttp.lib
crypt32.lib
bcrypt.lib

Is it correct way of doing this? Also does linking against above Windows libraries makes it no cross-platform any longer?

Thanks a lot!