Skip to content

Avoid merge conflicts in build-js.sh#1286

Merged
kripken merged 3 commits intoWebAssembly:masterfrom
dcodeIO:js-build-noconflict
Nov 13, 2017
Merged

Avoid merge conflicts in build-js.sh#1286
kripken merged 3 commits intoWebAssembly:masterfrom
dcodeIO:js-build-noconflict

Conversation

@dcodeIO
Copy link
Copy Markdown
Contributor

@dcodeIO dcodeIO commented Nov 13, 2017

Changes the EXPORTED_FUNCTIONS parameter from a single to multiple lines. This not only makes it easier to extend by a human but also prevents some merge conflicts.

#1280 and #1274 would have to be updated if this one lands earlier, which I'd prefer.

Changes the EXPORTED_FUNCTIONS parameter from a single to multiple lines. This not only makes it easier to extend by a human but also prevents some merge conflicts.
@dcodeIO
Copy link
Copy Markdown
Contributor Author

dcodeIO commented Nov 13, 2017

Seems the AppVeyor build failed for a different reason.

@kripken
Copy link
Copy Markdown
Member

kripken commented Nov 13, 2017

Good idea, thanks.

Sorry, I already merged one of those 2 PRs since I didn't read this one til later. Would you prefer to merge this in before the remaining one?

Btw, this will also be useful when we need to use that list more than once, which will be the case when we have a binaryen.wasm.js (binaryen.js but compiled code is wasm) which I've been planning to add, since even node.js LTS now has wasm support.

@dcodeIO
Copy link
Copy Markdown
Contributor Author

dcodeIO commented Nov 13, 2017

Should be good to merge once the checks complete. I just recently merged master when I noticed that the other one landed. I believe the second still needs some review updates anyway.

@kripken kripken merged commit 20b8b02 into WebAssembly:master Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants