| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
Python scripts were previously checked out with CRLF line endings by default on Windows (unless configured otherwise globally), leading to problems with the shebang not being correctly recognized when mounted into WSL and trying to run `./thescript.py` without prepending `python3` (just like `*.sh` files and `bash` that have already been addressed). NFC except that it helps in mixed setups.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This PR enables compiling Binaryen to WebAssembly when building binaryen.js. Since WebAssembly is best compiled and instantiated asynchronously in browsers, it also adds a new mechanism to tell if respectively when the module is ready by means of one of the following:
// Using a promise
const binaryen = require("binaryen");
binaryen.ready.then(() => {
... use normally ...
});
// Using await
const binaryen = require("binaryen");
(async () => {
await binaryen.ready;
... use normally ...
})();
// Where top-level await is available
const binaryen = await require("binaryen").ready;
... use normally ...
One can also tell if Binaryen is already ready (for example when assuming it in follow-up code) by:
if (/* we already know that */ binaryen.isReady) {
... use normally ...
} else {
throw Error("Binaryen is supposed to be ready here but isn't");
}
The JS test cases have been updated accordingly by wrapping everything in a test function and invoking it once ready. Documentation will have to be updated as well to cover this of course. New file size is about 2.5mb, even though the Wasm becomes inlined into the JS file which makes distribution across different environments a lot easier.
Also makes building binaryen (to either js or wasm) emit binaryen.js, and not binaryen_js.js etc.
Supersedes and thus fixes #1381
With .ready it also fixes #2452
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is an alternative to #2361 in that it only implements reusing BINARYEN_API
so we don't have to list all the functions in build-js.sh. Differs in that it
keeps the sh file relatively straight forward without going overboard with bash
functionality. Also adds various quotes in case of whitespace in paths and makes
it so that *.sh files always use LF line endings to ease Windows support. For
instance, I am pulling the repository in Windows but compile in WSL, which, if
Git isn't properly configured to check out line endings as-is, would otherwise
break the sh files.
Fixes #2361.
|
| |
|
|
|
|
|
|
|
|
|
| |
Update build-js.sh to output to `out` directory. This is district
from the `bin` directory which is used by the cmake build and may or
may not live in the source tree. The `out` directory currently always
lives in the source tree.
As a followup change I hope to additionally move all test outout into
this tree.
See #2104
|
| |
|
| |
following #1859
|
| |
|
|
| |
Otherwise `git grep` is rendered rather useless.
|
| |
|
