emscripten-core / emscripten-core/emscripten
Permanent integration of Emscripten with autotools
- Dominant language
- C++
- Stars
- 27.6k
- Forks
- 3.6k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 105
Description
Ideally, what is the way to integrate permanently Emscripten/wasm in an autotools framework? (e.g. to have Emscripten platform constant detection fixed) so that host/target/build args can accept natively emscripten-wasm32 or sth like that
Should Emscripten strive to upstream to https://https.git.savannah.gnu.org/git/config.git/ `config.sub` and `config.guess` scripts? Or is this repo irrelevant?
Contributor guide
Research direction
Start by reading the autotools integration and the config.sub/config.guess scripts referenced in the issue, then compare how Emscripten/wasm32 is currently detected. Determine whether permanent host/target/build support belongs upstream in GNU config.sub and config.guess or in this repository. Done means a documented, accepted integration path for native emscripten-wasm32 arguments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100