Why so many dependencies to "just" build the AWS library?

[lermy3d]

I cannot build the AWS SDK for C++, cmake requires make, make requires MinGW-w64... why pre-compiled libraries are not provided?

[jmklix]

These are common dependencies required for building C++ projects. While you can find this SDK on some C++ package managers, that is not the recommended way to consume it. We recommend that you consume this sdk from source(GitHub) and then compile it to fit your exact needs.

If you haven't already, please check out our developer guide.

If you have any questions about building or using this SDK, feel free to ask.

Additionally, here is a Reddit thread that discusses some good points as to why there aren't many package managers (with pre-compiled libraries) in the C++ world.

[lermy3d]

Thank you for your reply, the "Guide" is incomplete, installing cmake alone is not sufficient to compile out of the box making the AWS Readme Guide: incomplete.

If one install cmake alone and run the cmake config step you will get the following error: CXX Compiler ABI info - failed
After realizing it does not encounters a C compiler one could have easily thought that installing VStudio with the C++ Dev Workflow would fix this step but nope, that is still not enough.
The easiest way is to install msys2 and install cmake, make and the gcc compiler, then you would say: Finally! I am gonna build my dynamo DB client!! And you would be wrong again!

Once you run "cmake .." on mingw64 it will still fail saying you need Python3 and ZLIB, which are both missing.
Once you do so and add it all up to your env paths as one is used to, one would still be getting the same missing "python3" error even though is installed and added to the env path.

And 48hs later of troubleshooting we are still stuck and have not been able to start developing our app.
AWS has provided an incomplete guide without all the requirements to build their library, they need to add a list of requirements to their steps to make this process straightforward.

The current error:

[lermy3d]

You can get this by installing any version of Visual Studio and selecting Desktop development with C++ when installing.

Do you have to specifically check for anything there? Because I do have installed the "Desktop Dev C++" workload locally. So I do not see why the VStudio Generator is not appearing... let me reroute the current cmake I am using from mysys2 to the one that comes with vstudio, it could be that...

In effect, I was able to get a vstudio solution using vstudio cmake, although, in the step 3 of the guide I do not have any "Configure CMake Settings" option appearing there:

I will try a build all, and see if that works.

[lermy3d]

By the way, the command I used was: cmake .. -G "Visual Studio 17 2022" -DCMAKE_BUILD_TYPE=Release -DBUILD_ONLY="dynamodb"
Since we are only interested on the dynamodb client.

[lermy3d]

I made a clean cmake build and at least I now have several more project added to the solution, the "aws-c-common" had previous CMakeList.txt files from the mynsys2 build. I am trying now to build this:

Still no "Configure CMake Settings" but that is at least some progress.

[lermy3d]

Uhhmm... some errors while building:

Probably another project like "aws-c-common" that is a dependency?

[lermy3d]

Ok I discovered what was going on, I had to execute a recurse-submodules on git in the aws sdk cpp main folder for it to bring all dependencies... after that a it was able to generate the solution, and build it, with some test skipped or with errors, but we finally have our aws dynamo client library!!

Leaving the tests involved in case those are useful:

We also run the cmake install and it run with success!! I really appreciate all the assistance with our blocker!!