updated emsdk execution path in wasm makefile#21615
Open
ramyD wants to merge 1 commit into
Open
Conversation
wasm makefile is still assuming the emsdk_env.sh is being copied into the sdks/wasm folder (introduced in 708d194) but this is no longer the case (since 967a79e) and now the make -C sdks/wasm packager.exe target fails. The EMCC variable has been updated to work resolving a packager.exe or dotnet.js dependency (for example).
Contributor
|
Note that current wasm work happens in dotnet/runtime repo, the wasm stuff in mono/mono is obsolete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wasm makefile is still assuming the emsdk_env.sh is being copied into the sdks/wasm folder (introduced in 708d194) but this is no longer the case (since 967a79e) and now the make -C sdks/wasm packager.exe target fails. The EMCC variable has been updated to work resolving a packager.exe or dotnet.js dependency (for example).