-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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: fix on darwin #31650
aws-sdk-cpp: fix on darwin #31650
Conversation
buildInputs = [ cmake curl ]; | ||
buildInputs = [ cmake curl ] | ||
++ lib.optionals stdenv.isDarwin | ||
(with darwin.apple_sdk.frameworks; [ CoreAudio AudioToolbox ]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose we could do this, or just conditionally disable those SDKs. I think it's for Amazon Lex and Polly or something like that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably avoid depending on frameworks for this, since it's a dependency of nix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that was my concern, although Nix only builds the S3 subset of the SDK (so we could perhaps only enable the frameworks if someone wants all sub-SDKs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's aws-sdk-cpp.override { apis = ["text-to-speach"]; }
that needs the frameworks.
2656fb1
to
590cdf0
Compare
/cc @LnL7 Added a check for text-to-speech. It should be ready to merge now. |
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
Motivation for this change
This resolves the issues on macOS. Not sure why these frameworks are needed?