microsoft / microsoft/react-native-windows
Native modules could be built as vcxitems
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Building modules as individual libraries carries some penalties, both at build time (everything needs to be linked and resolved), as well as deployment-wise and at runtime (whole separate PE image, prevents folding with like code in the app binary).
For native modules that are distributed as binary, this seems inescapable.
However for modules that are source-distributed, a proposal would be to distribute them as vcxitems projects that get statically linked into the app.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing how source-distributed native modules are currently built and linked, then define the vcxitems approach and its build, deployment, and runtime acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100