-
|
Greetings! I need to use AWS SDK in a project that has four configurations "Debug, RelWithDebInfo, MinSizeRel, and Release" If I follow the instructions to build and install the SDK from source, it seems I can only have one configuration installed at a time.
I need to run both debug and release configurations of my code. What is the intended usage here? My project is currently in development and I am frequently switching between debug and release configurations. This seems like it would be a common use case but I'm having some difficulty getting this set up. Any input on best practices would be much appreciated. Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
You can build this sdk into two different folders and then point to each one when you want to switch between debug and release. i.e. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! That's what I've done for most other libraries I've worked with. I'm a bit confused by this one though. When building from source on windows the last step is to build INSTALL.vcxproj
Is there any way to change that path so that I get can build and release installations? Here are some things I've tried. I tried just making a copy of it so i have:
But then I'm not sure how to link them in cmakelists.txt. I have to modify the name of AWSSDKconfig.cmake in aws-cpp-sdk-all-debug\ to AWSSDKdebugconfig.cmake so that I can do:
but even then the first thing that cmake file does is:
I can comment that out and then cmake will find both packages. But now I have to link them. I tried something like this:
And that gives me this: CMake Error at source/projects/AWSTest3.hello-world/CMakeLists.txt:59 (target_link_libraries): I might be missing something in the docs, but in following the instructions in the getting started guide, I'm not clear on how to set up the solution you propose above. Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Joseph, Thanks again for your response. I've built the sdk as static libs and I'm having some difficulty getting the release/debug configurations set up with cmake. A few questions;
An example cmaklists.txt or any advice you can give about how to set up this linking in cmake would be invaluable. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
I was able to solve this by manually adding all the libs the SDK requires. I was not able to use cmakes findpackage function to find the debug and release versions of the SDK. If i tell cmake:
CMake will find the first one, and no matter what I tried, the second findpackage() would always refer back to the first package already loaded. So I attempted to manually add the .libs from aws-cpp-sdk/all/lib. This didn't work at first until I discovered that the findpackage scripts add additional libs that are not in those folders! Once I added ALL of the the libs the sdk requires, I was able to build successfully. Below is what I added to my project's cmakelists.txt in order to link to debug and release builds of the SDK with s3. Note that the debug build of the sdk does not include pdb files. This appears to be a known issue. So I added an additional line at the end to suppress LNK 4099 warnings that pdb files are missing. As long as I am certain that other libraries I use in my projects have pdb files this should not be problem.
|
Beta Was this translation helpful? Give feedback.
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
I was able to solve this by manually adding all the libs the SDK requires.
I was not able to use cmakes findpackage function to find the debug and release versions of the SDK. If i tell cmake:
CMake will find the first one, and no matter what I tried, the second findpackage() would always refer back to the first package already loaded.
So I attempted to manually add the .libs from aws-cpp-sdk/all/lib. This didn't work at first until I discovered that the findpackage scripts add additional libs that are not in those folders! Once I added ALL of the the libs the sdk requires, I was able to build successfully. Below is what I added to my project…