diff options
| author | Morten Sørvig <morten.sorvig@qt.io> | 2022-05-10 09:09:51 +0200 |
|---|---|---|
| committer | Morten Sørvig <morten.sorvig@qt.io> | 2022-05-12 16:34:24 +0200 |
| commit | b119f26a5663c5e3f82d82ad41e479a42115d954 (patch) | |
| tree | 99f07f2df890ed6cfb926fc0934b8235dbfbdf18 /mkspecs/wasm-emscripten/qmake.conf | |
| parent | bd8d3fb47ca685da9ce038bd6c6ee66e49ec9317 (diff) | |
wasm: enable WASM_BIGINT
JavaScripts's BigInt feature provides support for arbitrary-precision
integers. This makes it possible to represent 64-bit integers; the
standard JS Number type supports 32-bit integers only (or more
accurately 53-bit integers - see Number.MAX_SAFE_INTEGER).
Enable WASM_BIGINT which makes Emscripten map int64_t and uint64_t
to BigInt when interfacing with JavaScript code.
This removes one of the conditions which enables
wasm-emscripten-finalize.
Task-number: QTBUG-103352
Change-Id: Ia70d599daaf34c92695f5a2b61665e0c237e6b95
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
Reviewed-by: David Skoland <david.skoland@qt.io>
Diffstat (limited to 'mkspecs/wasm-emscripten/qmake.conf')
| -rw-r--r-- | mkspecs/wasm-emscripten/qmake.conf | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/mkspecs/wasm-emscripten/qmake.conf b/mkspecs/wasm-emscripten/qmake.conf index 270ab39559..140f2b4801 100644 --- a/mkspecs/wasm-emscripten/qmake.conf +++ b/mkspecs/wasm-emscripten/qmake.conf @@ -38,7 +38,8 @@ EMCC_COMMON_LFLAGS += \ --bind \ -s FETCH=1 \ -s MODULARIZE=1 \ - -s EXPORT_NAME=createQtAppInstance + -s EXPORT_NAME=createQtAppInstance \ + -s WASM_BIGINT=1 # The -s arguments can also be used with release builds, # but are here in debug for clarity. |