Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws-sdk-cpp build failure #20167

Closed
xanather opened this issue Sep 15, 2021 · 1 comment · Fixed by #20189
Closed

aws-sdk-cpp build failure #20167

xanather opened this issue Sep 15, 2021 · 1 comment · Fixed by #20189
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@xanather
Copy link
Contributor

AWS CPP SDK no longer builds since 92af1ff

Host Environment

  • OS: Windows
  • Compiler: MSVC 19.29.30038.1

To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe update
.\vcpkg.exe install aws-sdk-cpp[core,cloudformation,ec2,monitoring,ssm,s3,cloudfront,rds,cloudtrail,sns,lambda]:x64-windows

Failure logs
config-x64-windows-out.log

Seems that the AWS CRT C++ does not build, which is required for all aws sdk libraries.

CMake Error at CMakeLists.txt:87 (configure_file):
configure_file attempted to configure a file:
C:/Users/xanat/Documents/Files/Projects/system_monitor/third-party/vcpkg/buildtrees/aws-crt-cpp/src/c763da6810-ba58d2be12.clean/include/aws/crt/Config.h
into a source directory.

Additional context
I appreciate the work Microsoft does with this beautiful tool which makes C++ dependency management more bearable but is there potentially a more 'stable' release branch system I can use to avoid this breaking my continuous integration? Should I be using the tags releases found here instead: https://github.com/microsoft/vcpkg/releases ?

Thanks

@PhoebeHui PhoebeHui self-assigned this Sep 16, 2021
@PhoebeHui PhoebeHui added the category:port-bug The issue is with a library, which is something the port should already support label Sep 16, 2021
@PhoebeHui
Copy link
Contributor

@xanather, thanks for reporting this issue! I have submitted a PR to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants