Closed TheSharpOwl closed 1 year ago
cc @camarois
Thanks for posting this issue. This issue has been fixed now, you can use aws-sdk-cpp
in your project.
Installing aws-sdk-cpp
by vcpkg.
Elapsed time to handle aws-sdk-cpp:x64-windows: 4.812 min
Total install time: 7.201 min
The package aws-sdk-cpp:x64-windows provides CMake targets:
When using AWSSDK, AWSSDK_ROOT_DIR must be defined by the user.
find_package(AWSSDK CONFIG COMPONENTS core dynamodb kinesis s3 REQUIRED)
target_include_directories(main PRIVATE ${AWSSDK_INCLUDE_DIRS})
target_link_libraries(main PRIVATE ${AWSSDK_LIBRARIES})
OR
find_package(aws-cpp-sdk-core REQUIRED)
target_include_directories(main PRIVATE aws-cpp-sdk-core)
target_link_libraries(main PRIVATE aws-cpp-sdk-core)
find_package(AWSSDK CONFIG COMPONENTS core dynamodb kinesis s3 REQUIRED)
in CMake project, and all header files could be included in project correctly.
1> [CMake] -- Found Threads: TRUE
1> [CMake] -- Found aws-cpp-sdk-core
1> [CMake] -- Try finding aws-cpp-sdk-s3
1> [CMake] -- Found aws-cpp-sdk-s3
1> [CMake] -- Try finding aws-cpp-sdk-kinesis
1> [CMake] -- Found aws-cpp-sdk-kinesis
1> [CMake] -- Try finding aws-cpp-sdk-dynamodb
1> [CMake] -- Found aws-cpp-sdk-dynamodb
1> [CMake] -- Configuring done
1> [CMake] -- Generating done
Describe the bug Inside
[VCPKG_LOCATION]\vcpkg\installed\x64-windows\share\AWSSDK\AWSSDKConfig.cmake
(for me I am using x64-windows build but I remember the same issue with static one). There are 2 problems:which takes it directly to the next lines printing that:
which takes it to print this (in the lines next)
Link to the file in the aws-cpp-sdk repo
Environment
To Reproduce Steps to reproduce the behavior:
./vcpkg.exe install aws-sdk-cpp[s3]:x64-windows
find_package(AWSSDK CONFIG REQUIRED COMPONENTS s3)
(It should be the same problem without specifyingCOMPONENTS
but reporting exactly what happened to me)Expected behavior CMake output:
Failure logs None it's the cmake output only
Additional context I noticed also that
AWSSDK_PLATFORM_PREFIX
CMake variable is empty Also what I think could fix it: Maybe some CMake variables they used can be set such that one of the options written infind_file
would be parsed to the path containing the header and the lib file (also attention should be paid to cases ofwindows-x64
orwindows-x64-static
to have different values for CMake variables according to the chosen installed version with vcpkgFix for now: Specify the path yourself example for me:
"[installation_path_for_vcpkg]/vcpkg/installed/x64-windows/include/aws/core"
"[installation_path_for_vcpkg]/vcpkg/installed/x64-windows/debug/lib"
Also don't forget to change the
x64-windows
part if you use another one and release be added the same way for the library part.