You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/source/docs/tools_reference/emsdk.rst
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,8 @@ The following topics explain how to perform both common and advanced maintenance
124
124
How do I just get the latest SDK release?
125
125
-----------------------------------------
126
126
127
-
Use the ``update`` argument to fetch the current registry of available tools, and then specify the ``latest`` install target to get the most recent SDK: ::
127
+
Use the ``update`` argument to fetch the current registry of available tools,
128
+
and then specify the ``latest`` install target to get the most recent SDK: ::
128
129
129
130
# Fetch the latest registry of available tools.
130
131
./emsdk update
@@ -138,17 +139,19 @@ Use the ``update`` argument to fetch the current registry of available tools, an
138
139
How do I install a specific version?
139
140
------------------------------------
140
141
141
-
Use the commands above, replacing ``latest`` with the version you want, for example: ::
142
+
Use the commands above, replacing ``latest`` with the version you want, for
143
+
example: ::
142
144
143
145
./emsdk install 4.0.7
144
146
./emsdk activate 4.0.7
145
147
146
148
(you may need to do ``./emsdk update`` before).
147
149
148
150
Each release also has an *asserts version* which is built with more runtime
149
-
checks in LLVM and Binaryen. This can be useful if you think you have encountered a bug in one of these tools. The names of
150
-
asserts versions are the same as release versions, with an added suffix of
151
-
``-asserts``, e.g. ``4.0.7-asserts``, which you can use with: ::
151
+
checks in LLVM and Binaryen. This can be useful if you think you have
152
+
encountered a bug in one of these tools. The names of asserts versions are the
153
+
same as release versions, with an added suffix of ``-asserts``, e.g.,
0 commit comments