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
Remove explicit support for JAVA and running closure compiler via java (#20919)
It should still be possible for a user to explictly run the java
version of closure using `EMCC_CLOSURE_ARGS=--platform=java` or
`--closure-args=--platform=java`, but this isn't something we need to
have explict support for and its not something we test.
Copy file name to clipboardExpand all lines: site/source/docs/building_from_source/verify_emscripten_environment.rst
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,14 +21,15 @@ Open a terminal in the directory in which you installed Emscripten (on Windows o
21
21
22
22
.. note:: On Windows, invoke the tool with **emcc** instead of **./emcc**.
23
23
24
-
For example, the following output reports an installation where Java is missing:
24
+
For example, the following output reports that the correct version of clang
25
+
could not be found:
25
26
26
27
.. code-block:: none
27
28
:emphasize-lines: 3
28
29
29
30
emcc (Emscripten GCC-like replacement + linker emulating GNU ld) 1.21.0
30
31
shared:INFO: (Emscripten: Running sanity checks)
31
-
shared:WARNING: java does not seem to exist, required for closure compiler. -O2 and above will fail. You need to define JAVA in .emscripten
32
+
emcc: warning: LLVM version for clang executable "/usr/bin/clang" appears incorrect (seeing "16.0", expected "18") [-Wversion-check]
32
33
33
34
At this point you need to :ref:`Install and activate <fixing-missing-components-emcc>` any missing components. When everything is set up properly, ``emcc ---check`` should give no warnings, and if you just enter ``emcc`` (without any input files), it will give an error ::
Copy file name to clipboardExpand all lines: site/source/docs/tools_reference/emcc.rst
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -259,7 +259,6 @@ Options that are modified or new in *emcc* are listed below:
259
259
260
260
- Consider using ``-sMODULARIZE`` when using closure, as it minifies globals to names that might conflict with others in the global scope. ``MODULARIZE`` puts all the output into a function (see ``src/settings.js``).
261
261
- Closure will minify the name of `Module` itself, by default! Using ``MODULARIZE`` will solve that as well. Another solution is to make sure a global variable called `Module` already exists before the closure-compiled code runs, because then it will reuse that variable.
262
-
- If closure compiler hits an out-of-memory, try adjusting ``JAVA_HEAP_SIZE`` in the environment (for example, to 4096m for 4GB).
263
262
- Closure is only run if JavaScript opts are being done (``-O2`` or above).
0 commit comments