microsoft / microsoft/react-native-windows
Use deterministic compiler/linker flags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
We've had a few people hit an issue where they wrongly have a RNW in node_modules in their NM and the example app, and they build both and when packaging they get a conflict. They shouldn't have 2 of them but: if we did use deterministic compiler/linker flags then this would not be a problem assuming both MRN are built with the same options
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 describes conflicting RNW builds from node_modules and the example app during packaging, but names no files or tests. Start by locating the compiler and linker configuration for both builds, then determine whether shared deterministic flags can make their outputs compatible. Done means packaging no longer encounters a conflict when both builds use the same options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100