Building Library Dependencies Separately

Open
#113 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, cpp
Domain
cloud

Research direction

The issue names no repository files, tests, or entry points. Begin by locating the runtime and dependency documentation for C++ Lambda functions, then document the required platform and GNU C Library ABI expectations for separately built dynamic libraries.

Written by the indexing model from the issue text.

Description

Hello,
If my lambda function has a c++ library dependency that I am building separately, and that will be dynamically loaded, what platform should I build the library dependency for? Linux ABI x86_64?
What happens with the GNU C Library ABI?
Will this be taken care of by the runtime as well?
I will be using the same platform to build those dependencies and to build the lambda function.

Thank you very much!

Dominant language
C++
Stars
465
Forks
98
Avg merge
1h 16m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-lambda-cpp

All issues in awslabs/aws-lambda-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.