Skip to content

Commit c56f260

Browse files
authored
Update README.md after #1166. NFC (#1172)
1 parent ae2664b commit c56f260

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -136,11 +136,11 @@ using git, and compile the package on demand.
136136
When you run `emsdk list`, it will group the Tools and SDKs under these two
137137
categories.
138138

139-
To obtain and build latest upstream wasm SDK from source, run
139+
To obtain and build latest wasm SDK from source, run
140140

141141
```
142-
emsdk install sdk-upstream-main-64bit
143-
emsdk activate sdk-upstream-main-64bit
142+
emsdk install sdk-main-64bit
143+
emsdk activate sdk-main-64bit
144144
```
145145

146146
You can use this target for example to bootstrap developing patches to LLVM,
@@ -156,7 +156,7 @@ https://emscripten.org/docs/contributing/developers_guide.html?highlight=develop
156156
### When working on git branches compiled from source, how do I update to a newer compiler version?
157157

158158
Unlike tags and precompiled versions, a few of the SDK packages are based on
159-
"moving" git branches and compiled from source (e.g. sdk-upstream-main,
159+
"moving" git branches and compiled from source (e.g. sdk-main,
160160
sdk-main, emscripten-main, binaryen-main). Because of that, the
161161
compiled versions will eventually go out of date as new commits are introduced
162162
to the development branches. To update an old compiled installation of one of
@@ -198,11 +198,11 @@ where you directly interact with the github repositories. This allows you to
198198
obtain new features and latest fixes immediately as they are pushed to the
199199
github repository, without having to wait for release to be tagged. You do not
200200
need a github account or a fork of Emscripten to do this. To switch to using the
201-
latest upstream git development branch `main`, run the following:
201+
latest git development branch `main`, run the following:
202202

203203
emsdk install git-1.9.4 # Install git. Skip if the system already has it.
204-
emsdk install sdk-upstream-main-64bit # Clone+pull the latest emscripten-core/emscripten/main.
205-
emsdk activate sdk-upstream-main-64bit # Set the main SDK as the currently active one.
204+
emsdk install sdk-main-64bit # Clone+pull the latest emscripten-core/emscripten/main.
205+
emsdk activate sdk-main-64bit # Set the main SDK as the currently active one.
206206

207207
### How do I use my own Emscripten github fork with the SDK?
208208

0 commit comments

Comments
 (0)