Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dotnet/runtime
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: radekdoulik/runtime
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: pr-readme-clarify-mac-parts
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 1 file changed
  • 1 contributor

Commits on Jun 14, 2021

  1. Verified

    This commit was signed with the committer’s verified signature.
    turing85 Marco Bungart
    Copy the full SHA
    9b2baa2 View commit details
Showing with 7 additions and 5 deletions.
  1. +7 −5 src/mono/wasm/README.md
12 changes: 7 additions & 5 deletions src/mono/wasm/README.md
Original file line number Diff line number Diff line change
@@ -2,7 +2,7 @@

This depends on `emsdk` to be installed.

## emsdk
## emsdk on mac

* You can run `make provision-wasm`, which will install it to `$reporoot/src/mono/wasm/emsdk`.
Note: Irrespective of `$(EMSDK_PATH)`'s value, `provision-wasm` will always install into `$reporoot/src/mono/wasm/emsdk`.
@@ -21,7 +21,9 @@ Make sure to set `EMSDK_PATH` variable, whenever building, or running tests for

Windows build [requirements](https://github.com/dotnet/runtime/blob/main/docs/workflow/requirements/windows-requirements.md)

## Building
If `EMSDK_PATH` is not set, the `emsdk` should be provisioned automatically during the build.

## Building on mac

* To build the whole thing, with libraries:

@@ -33,7 +35,7 @@ Windows build [requirements](https://github.com/dotnet/runtime/blob/main/docs/wo

### Note: Additional msbuild arguments can be passed with: `make build-all MSBUILD_ARGS="/p:a=b"`

### Windows
### Bulding on windows

* To build everything

@@ -103,7 +105,7 @@ Examples of running tests for individual libraries:
`.\dotnet.cmd build /t:Test /p:TargetOS=Browser src\libraries\System.Collections.Concurrent\tests`
`.\dotnet.cmd build /t:Test /p:TargetOS=Browser /p:JSEngine="SpiderMonkey" src\libraries\System.Text.Json\tests`

### Browser tests
### Browser tests on mac

Or they can be run with a browser (Chrome):

@@ -125,7 +127,7 @@ The wrapper script used to actually run these tests, accepts:

### Note: Additional msbuild arguments can be passed with: `make .. MSBUILD_ARGS="/p:a=b"`

## Debugger tests
## Debugger tests on mac

Debugger tests need `Google Chrome` to be installed.