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
+19-2Lines changed: 19 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -121,8 +121,9 @@ The following topics explain how to perform both common and advanced maintenance
121
121
.. _emsdk-get-latest-sdk:
122
122
123
123
124
-
How do I just get the latest SDK?
125
-
---------------------------------
124
+
How do I just get the latest SDK release?
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
128
128
129
# Fetch the latest registry of available tools.
@@ -134,7 +135,23 @@ Use the ``update`` argument to fetch the current registry of available tools, an
134
135
# Set up the compiler configuration to point to the "latest" SDK.
135
136
./emsdk activate latest
136
137
138
+
How do I install a specific version?
139
+
------------------------------------
140
+
141
+
Use the commands above, replacing ``latest`` with the version you want, for example: ::
142
+
143
+
./emsdk install 4.0.7
144
+
./emsdk activate 4.0.7
145
+
146
+
(you may need to do ``./emsdk update`` before).
147
+
148
+
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: ::
0 commit comments