Extend shared simdutf flag to v8
Open
Beginner friendly
Nobody has claimed this yet.
feature request
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
What is the problem this feature will solve?
configure.py has --shared-simdutf* flags, but now v8 embeds another copy of simdutf as well.
What is the feature you are proposing to solve the problem?
It would be awesome if tools/v8_gypfiles/v8.gyp was updated to allow linking v8 to the shared simdutf copy.
What alternatives have you considered?
No response
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
Start with configure.py's existing --shared-simdutf* flags and tools/v8_gypfiles/v8.gyp. Trace how the shared simdutf option is represented in the V8 build configuration, then update the V8 target so it can use the shared copy. Done means the V8 build path honors the flag without embedding another simdutf copy; verify by configuring and building with the shared option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js, python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100