Version numbering questions about binaryen/emscripten

[Joan Karadimov]

I'm trying to figure out the version numbering of binaryen and how that corresponds to emscripten. Can anyone help me with these questions...

1. Why is there an overlap between the versions of binaryen and emscripten?
2. Why are there versions of binaryen that do not match the emscripten version scheme (e.g. version_87 vs 1.38.32)?
3. Are only the identically numbered versions emscriopten/binaryen compatible?
4. Why do the emscripten-numbered versions of binaryen stop at 1.38.32?

[Alon Zakai]

The current docs about this are here:

https://github.com/emscripten-core/emscripten/blob/incoming/docs/process.md#packaging-emscripten

Basically, in the past we tagged the binaryen repo with emscripten versions, to make it easy to see how things matched up. Our old CI would find those tags and build them. In the new CI, there is no need for that, see the DEPS file mentioned in that link. That file shows how an emscripten version maps to all relevant repos (including binaryen, and also llvm, etc.). So there is no need to tag the binaryen repo with emscripten versions, and we've stopped doing so.

The version_* tags are binaryen's own versions. Those tags are used for releasing binaryen.js for example, https://www.npmjs.com/package/binaryen

- Alon

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/c4bc1b6f-1bb4-4ef0-9431-9acba655c063%40googlegroups.com.