ed26c01be1
ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com> |
||
|---|---|---|
| .. | ||
| prj | ||
| ExternalProject_rhino.mk | ||
| Makefile | ||
| Module_rhino.mk | ||
| OfficeScriptInfo.java | ||
| Package_rhino.mk | ||
| README | ||
| rhino1_5R5-find_swing.patch | ||
| rhino1_5R5-updateToolTip.patch | ||
| rhino1_5R5.patch | ||
| UnpackedTarball_rhino.mk | ||
JavaScript engine/interpreter written in Java, used to provide JavaScript extensions. The Scripting Framework makes use of the Rhino ([http://www.mozilla.org/rhino/]) JavaScript interpreter, available under the Mozilla Public License ([http://www.mozilla.org/MPL/MPL-1.1.html]). In addition, to support the debugging of scripts contained in OpenOffice.org documents, we have modified the Java source file Main.java. The Rhino source tarball is unpacked and patched with the modified code. The Rhino Jar file (js.jar) is then built (download/swingExSrc.zip is unpacked and built as part of this procesS) and delivered to the solver. The file rhino1_5R5.patch contains the changes made in order to build Rhino. The patch was generated using the command: diff -wurN