Closed JasonLukose closed 6 years ago
Update: it works with VS2015.
Thanks for reporting this problem. Some of the Nuget packages for vs2017 are missing, we fixed it. It will be available on Nuget soon.
Hi, Nuget packages for vs2017 has been updated, Thank you!
Thanks! It works great. I did have to make the reference packages statically linked and not dynamically linked after I re installed the core and sqs. All in all, works well!
@JasonLukose What will happen when you dynamically link the libs?
It will error with the following error if both are DLL @singku
Error LNK2001 unresolved external symbol "char const * const Aws::Http::CONTENT_TYPE_HEADER"
(?CONTENT_TYPE_HEADER@Http@Aws@@3PEBDEB)
Sorry, saw this late! @singku
@JasonLukose We compiled above code with vs2017 and Nuget package, both dynamic and static link can work just fine. By the way, we select the link method in "Propoerties->Referenced Packages"
Using windows 10, with Visual Studio 2017.
I used Nuget to get the SDK and tried running this:
However, it seems that visual studio has linking errors when trying to do InitAPI and shutdownAPI.
1>------ Build started: Project: Project1, Configuration: Debug Win32 ------ 1>Source.cpp 1>Source.obj : error LNK2019: unresolved external symbol "void __cdecl Aws::InitAPI(struct Aws::SDKOptions const &)" (?InitAPI@Aws@@YAXABUSDKOptions@1@@Z) referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol "void __cdecl Aws::ShutdownAPI(struct Aws::SDKOptions const &)" (?ShutdownAPI@Aws@@YAXABUSDKOptions@1@@Z) referenced in function _main
1>C:\Users\Jason\source\repos\Project1\Debug\Project1.exe : fatal error LNK1120: 2 unresolved externals 1>Done building project "Project1.vcxproj" -- FAILED. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
There does not seem to be any documentation with Visual Studio 2017