Closed emnul closed 3 months ago
The runtime does not depend on OpenSSL. It's probably a transitive dependency from one of the dependencies in your project, most likely alloy
.
There are some recommendations on how to deal with this kind of problems in Cargo Lambda's documentation: https://www.cargo-lambda.info/guide/cross-compiling.html#known-cross-compilation-issues
Yup, you're totally right. Alloy has the following dep: reqwest = { version = "0.12", default-features = false }
which is known to cause build issues with cargo lambda.
Thanks for making this more clear!
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one.
I have a project with the following Cargo.toml file:
When I try to compile the project with cargo lambda build I get the following error:
Adding openssl to my Cargo.toml fixes this issue, but I'd like to know what the root cause of the issue is so I can avoid an unnecessary dependency if possible.
It seems lambda-runtime depends on openssl for... reasons??
cargo tree
I suspect the native binaries on my local machine aren't playing nice with cargo lambda's cross compilation. Any help would be greatly appreciated.
Thanks!