Re: how to disable binaryen in .emscripten config file

[Alon Zakai]

There isn't an option for that. You might try to modify emcc.py to make it not call binaryen. I think that could work - but you'd get a much less optimized wasm, which on a project of that size could be a problem.

It's probably best to build binaryen manually - it's much simpler and smaller than building fastcomp or any LLVM fork. Just cmake, make should work.

On Wed, Aug 26, 2020 at 8:11 AM r0l...@freemail.hu <r0l...@freemail.hu> wrote:

Hi All,

I'm trying to crosscompile qt5 (5.15) with emscripten and they require emscripten 1.39.8 with fastcomp backend. However, that version cannot be built from source (which is a pity since prebuilt linux binary won't work on my NetBSD box). So I built fastcomp manually and pointed LLVM_ROOT to it. It works fine until qt stops during crosscompiling and I can see from the config.log that it's missing stuff from binaryen (like wasm-opt) which I guess is due to the fact that it compiles with WASM=1. Indeed, in the .emscripten config file BINARYEN_ROOT is also set since 1.39.8 is not fastcomp specific.

So is it possible to set an environment variable in .emscripten that disables binaryen and results as if my emscripten installation has only fastcomp backend?

Thanks&regards,

r0ller

--
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/ad6b5d54-8a6c-4a0e-a8df-321d19c5a33an%40googlegroups.com.

[r0ller r0ller]

Hi Alon,

Thanks for your answer! Good to know that it's not possible. However, it turned out that it's not even necessary as I misunderstood the docs since qt is no more bound to fastcomp backend.

Best regards,

r0ller

2020. augusztus 27., csütörtök 18:25:32 UTC+2 időpontban Alon Zakai a következőt írta:

There isn't an option for that. You might try to modify emcc.py to make it not call binaryen. I think that could work - but you'd get a much less optimized wasm, which on a project of that size could be a problem.

It's probably best to build binaryen manually - it's much simpler and smaller than building fastcomp or any LLVM fork. Just cmake, make should work.

On Wed, Aug 26, 2020 at 8:11 AM r0l...@freemail.hu <r0l...@freemail.hu> wrote:

Hi All,

I'm trying to crosscompile qt5 (5.15) with emscripten and they require emscripten 1.39.8 with fastcomp backend. However, that version cannot be built from source (which is a pity since prebuilt linux binary won't work on my NetBSD box). So I built fastcomp manually and pointed LLVM_ROOT to it. It works fine until qt stops during crosscompiling and I can see from the config.log that it's missing stuff from binaryen (like wasm-opt) which I guess is due to the fact that it compiles with WASM=1. Indeed, in the .emscripten config file BINARYEN_ROOT is also set since 1.39.8 is not fastcomp specific.

So is it possible to set an environment variable in .emscripten that disables binaryen and results as if my emscripten installation has only fastcomp backend?

Thanks&regards,

r0ller

--
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-discuss+unsubscribe at googlegroups.com.