You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by na...@apache.org on 2006/11/28 11:06:13 UTC
svn commit: r479971 - in /harmony/standard/site:
docs/subcomponents/drlvm/getting_started.html
xdocs/subcomponents/drlvm/GettingStarted.html
xdocs/subcomponents/drlvm/getting_started.xml
Author: nadinem
Date: Tue Nov 28 02:06:12 2006
New Revision: 479971
URL: http://svn.apache.org/viewvc?view=rev&rev=479971
Log:
Resolve H-2150: remove old/redundant info and screenshots
Modified:
harmony/standard/site/docs/subcomponents/drlvm/getting_started.html
harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html
harmony/standard/site/xdocs/subcomponents/drlvm/getting_started.xml
Modified: harmony/standard/site/docs/subcomponents/drlvm/getting_started.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/getting_started.html?view=diff&rev=479971&r1=479970&r2=479971
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/getting_started.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/getting_started.html Tue Nov 28 02:06:12 2006
@@ -36,7 +36,7 @@
- <title>Apache Harmony - Getting Started</title>
+ <title>Apache Harmony - Getting Started with DRLVM</title>
<link rel="Stylesheet" type="text/css" href="site.css"/>
</head>
@@ -221,616 +221,196 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-
+
-->
-
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-
-
-<html>
-<head>
- <meta http-equiv="Content-Type"
- content="text/html; charset=us-ascii">
-
- <title>Getting Started with DRL</title>
- <link rel="Stylesheet"
- type="text/css"
- media="all"
- href="site.css">
-</head>
-
-<body> <h1>
- <a id="Top" name="Top"></a>Getting Started with DRL</h1>
-
- <p>The Dynamic Runtime Layer (DRL) is a clean-room
- implementation of the Java<a href="#*">*</a> 2 Platform,
- Standard Edition (J2SE<a href="#*">*</a>) 1.5.0. The design
- keystones of the DRL virtual machine (VM) are clarity of
- concept, modularity, extensibility, and competitive
- performance. This document describes the first version of DRL
- deployed in March 2006.</p>
-
- <p>To quickly start with DRL, walk through the provided
- scenarios. It is recommended that you strictly follow the
- instructions of this guide to ensure system stability and
- anticipated results.</p>
-
- <p class="TOC"><a href="#Overview">Overview</a></p>
-
- <p class="TOC"><a href="#Before_You_Start">Before You
- Start</a></p>
-
- <p class="TOC"><a href="#Running_Hello">Running an
- Application</a></p>
-
- <p class="TOC"><a href="#Eclipse_Hello_world">Running an
- Application in Eclipse</a></p>
-
- <p class="TOC"><a href="#Eclipse_debug_scenario">Debugging an
- Application in Eclipse</a></p>
-
- <p class="TOC"><a href="#Command_line_Options">Command-line
- Options</a></p>
-
- <h2><a name="Overview"></a>Overview</h2>
-
- <p>In the Getting Started document, the first scenario
- illustrates running an application with DRL, and the two others
- demonstrate running and debugging an application in the
- Eclipse<a href="#*">*</a> integrated development environment.
- DRL is used to run both Eclipse<a href="#*">*</a> and the new
- application. After completing this guide, you will be able to
- run and debug your own applications with DRL.</p>
-
- <h2><a name="Before_You_Start"></a> Before You Start</h2>
-
- <p>By following the instructions in the <code>README.txt</code>
- file, install DRL and run acceptance tests to make sure that
- the installation is complete. You will have the default
- configuration installed on your system. To change the default
- DRL settings, use the <a href=
- "#Command_line_Options">Command-line Options</a>
- listed in this document.</p>
- <h3>Notations Conventions</h3>
- <p>When following the scenarios described below, please make the following adjustments: </p>
- <ul>
- <li>
- In the paths indicated, the slash \ is in the Windows<a href="#*">*</a> style,
- and / is in the Linux<a href="#*">*</a> style. Verify that your paths are correct when doing cut-and-paste.
- <li>The file <code>eclipse.bat</code> on Windows<a href="#*">*</a> corresponds to the file <code>eclipse.sh</code> on Linux<a href="#*">*</a>.
-</ul>
-<p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Running_Hello"></a>Running an Application</h1>
-
- <p>This scenario provides step-by-step instructions on running
- the <code>Hello</code> application in the Windows<a href=
- "#*">*</a> or the Linux<a href=
- "#*">*</a> console. The scenario uses the
- <code>Hello.class</code> Java<a href=
- "#*">*</a> class distributed with the
- product as the sample Java<a href=
- "#*">*</a> application.</p>
-
- <ol>
- <li>To start DRL, change your current directory to the
- <code><<b>installation folder</b>>\bin</code>
- directory.
-
- <li>Check that you have files <code>ij.exe</code> on Windows<a href=
- "#*">*</a> or <code>ij</code> on Linux<a href=
- "#*">*</a> and
- <code>Hello.class</code> in the <code>\bin</code>
- directory.
- <br>
- On Linux<a href="#*">*</a>, make sure that you can run applications
- and load dynamic libraries from the current directory.
- For example:
- <pre>export PATH=.:${PATH}
-export LD_LIBRARY_PATH=${PWD}:${LD_LIBRARY_PATH}</pre>
-
- If you are using the Intel(R) C++ compiler, make sure
- the <code>LD_LIBRARY_PATH</code> contains location of the ICC libraries.
-
- <li>
- Run the <code>Hello</code> application by entering:
- <pre>
-ij Hello
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
+ <title>
+ Getting Started with DRLVM
+ </title>
+ <link rel="Stylesheet" type="text/css" media="all" href="site.css" />
+ </head>
+ <body>
+ <h1>
+ <a id="TOP" name="TOP"></a>Getting Started with DRLVM
+ </h1>
+ <p>
+ The Dynamic Runtime Layer virtual machine (DRLVM) is a clean-room implementation of the
+ Java<a href="#*">*</a> virtual machine for Java 2 Platform, Standard Edition (J2SE<a
+ href="#*">*</a>) 1.5.0. This document gives tips on how to start using
+ the DRL virtual machine (VM). Use this page to learn where to get the
+ code and how to use it. For documentation on the Harmony Java<a
+ href="#*">*</a> class libraries, see the <a
+ href="../classlib/index.html">classlib page</a>.
+ </p>
+ <p>
+ To quickly start with DRL, read this page and follow the instructions.
+ It is recommended that you strictly follow the instructions of this
+ guide to ensure system stability and anticipated results. After
+ completing this guide, you will be able to run and debug your own
+ applications with DRLVM.
+ </p>
+ <h2>
+ <a id="Overview" name="Overview"></a>Overview
+ </h2>
+ <p>
+ For a definition of the DRL virtual machine and links to all docs
+ describing it, see the DRLVM <a href="index.html">component page</a>.
+ For instructions on how to get and build the code, and configure your
+ environment, please visit the <a
+ href="../../quickhelp_users.html">Getting Started for Users</a> page.
+ If you fail to build the source code or come across other problems, go
+ to our project <a href="http://wiki.apache.org/harmony/"
+ target="_blank">Wiki resource</a> and search for your issue on the <a
+ href="http://wiki.apache.org/harmony/DrlvmBuildTroubleshooting"
+ target="_blank">DrlvmBuildTroubleshooting</a> page. If no known issue
+ matches your problem, please write to the mailing list or add your
+ issue to the wiki page.
+ </p>
+ <p>
+ The README file supplied with the source code and the Quick Help
+ instructions enable you to build the VM source code in the default
+ configuration. To modify the code behavior, use the available
+ command-line options, as indicated in the <a
+ href="http://wiki.apache.org/harmony/DrlvmCommandLineOptions"
+ target="_blank">Wiki command-line options page</a>. Read further
+ for illustrations of command-line options usage.
+ </p>
+ <h1>
+ <a id="Running_Hello" name="Running_Hello"></a>Running an Application
+ </h1>
+ <p>
+ This scenario provides step-by-step instructions on running a
+ <code>Hello</code> application in the Windows<a href="#*">*</a> or the
+ Linux<a href="#*">*</a> console. The scenario uses a sample
+ <code>Hello.class</code> Java<a href="#*">*</a> class for illustration.
+ Please use your own application instead.
+ </p>
+ <ol>
+ <li>
+ To start DRL, change your current directory to the
+ <code><<b>installation folder</b>>\bin</code> directory.
+ </li>
+ <li>
+ Check that you have files <code>java.exe</code> on Windows<a
+ href="#*">*</a> or <code>java</code> on Linux<a href="#*">*</a> and
+ <code>Hello.class</code> in the <code>\bin</code> directory.<br />
+ On Linux<a href="#*">*</a>, make sure that you can run
+ applications and load dynamic libraries from the current directory.
+ If you are using the Intel(R) C++ compiler, make sure the
+ <code>LD_LIBRARY_PATH</code> variable contains location of the ICC
+ libraries.
+ </li>
+ <li>
+ Run the <code>Hello</code> application by entering:
+<pre>
+java Hello
</pre>
-
- <p>You will see “<i>Hello World!</i>" printed on
- the screen. This means that you have successfully
- launched the virtual machine, and that
- it has processed the <code>Hello.class</code> Java<a href=
- "#*">*</a>
- class to execute the <code>Hello</code>
- application.</p>
-
- </ol>
-<p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Eclipse_Hello_world"></a> Running an Application
- in Eclipse</h1>
-
- <p>This scenario provides step-by-step instructions on running
- a Java application in the Eclipse<a href="#*">*</a>
- environment. In the scenario, you will launch
- Eclipse<a href="#*">*</a>, create a new project and a new
- Java class within this project, and finally you will run the
- new application.</p>
-
- <ol>
- <li>Download the Eclipse<a href="#*">*</a> 3.1.1 package
- at <a href=
- "http://download.eclipse.org/eclipse/downloads/"
- target=
- "_blank">http://download.eclipse.org/eclipse/downloads/</a>,
- and unpack this distribution.
-
- <li>Set the environment variable <code>ECLIPSE_HOME</code>
- to point to the location of the Eclipse<a href="#*">*</a> installation directory.
- <br>
- On Linux<a href="#*">*</a>,
- if you are using the Intel(R) C++ compiler, additionally set the <code>LD_LIBRARY_PATH</code>
- variable to point to the location of the ICC libraries.
-
- <li>On Windows<a href="#*">*</a>, edit the Eclipse<a href="#*">*</a> launch script
- <code><<b>installation
- folder</b>>/bin/eclipse.bat:</code> make sure
- that <code>BUILD_HOME</code> variable points to the
- <code><<b>installation folder</b>>.
-
- <li>Start Eclipse<a href="#*">*</a> by launching Eclipse starter script:
- <br>on Windows<a href="#*">*</a>:
- <code><<b>installation folder</b>>/bin/eclipse.bat</code>;
- <br>on Linux<a href="#*">*</a>:
- <code><<b>installation folder</b>>/bin/eclipse.sh</code>.
-
- <li>
- After running Eclipse<a href="#*">*</a> starter script, the
- <b>Workspace Launcher</b> dialog opens. Specify the
- path to your workspace directory. In the example, click
- <b>OK</b> to set the default path.
-
- <p style="text-align: center"><img border="0"
- width="438"
- height="244"
- src="images/workspace_launcher.gif"
- alt=
- "Specifying the Workspace directory for the Project"></p>
-
-
- <li>The <b>Welcome</b> page of the Eclipse<a href="#*">*</a>
- environment opens. Close the window to proceed.
-
- <li>
- Create a new project via <b>File > New >
- Project…</b>
-
- <p>The <b>New project</b> dialog appears. Select
- <b>Java Project</b>, click <b>Next</b> and type the
- project name in the <b>New Java Project</b> field, in
- the example, <i>Hello</i>. Then click the <b>Finish</b>
- button.</p>
-
- <p style="text-align: center"><img border="0"
- width="500"
- height="555"
- src="images/new_project.gif"
- alt=
- "Dialog: New Java Project with Default Settings"></p>
-
- <p>When prompted to switch to the Java Perspective,
- click <b>Yes</b>.</p>
-
-
- <li>
- The <b>Package Explorer</b> tab opens in the left-hand
- part of the workspace with the name of your project
- displayed.
-
- <p style="text-align: center"><img border="0"
- width="691"
- height="609"
- src="images/package_explorer.gif"
- alt=
- "Eclipse Platform Workspace with the Package Explorer and the Hello Class">
- </p>
-
-
- <li>
- Create a new class via <b>File > New > Class
- <i>…</i></b>
-
- <p>The <b>New Java Class</b> wizard opens. Type in the
- class name, in the example, <i>HelloWorld</i> and
- select the <b>public static void main(String[]
- args)</b> check box at the bottom of the dialog
- window.</p>
-
- <p style="text-align: center"><img border="0"
- width="515"
- height="557"
- src="images/new_java_class.gif"
- alt=
- "Dialog New Java Class with Settings Configured as Required">
- </p>
-
-
- <li>
- You have created the <code>HelloWorld</code> class. The
- workspace gets updated with the class information as
- shown below.
-
- <p>In the <b>Package Explorer</b> window, you can see
- that the class is in the default package. The
- <b>Outline</b> window displays the one method of this
- class: the <code>main</code> method with an array of
- <code>String</code> parameters.</p>
-
- <p style="text-align: center"><img border="0"
- width="834"
- height="636"
- src="images/workspace1.gif"
- alt=
- "Workspace with the HelloWorld.java Class conent Displayed">
+ <p>
+ You will see “<i>Hello World!</i>" printed on the screen.
+ This means that you have successfully launched the virtual
+ machine, and that it has processed the <code>Hello.class</code>
+ Java<a href="#*">*</a> class to execute the <code>Hello</code>
+ application.
</p>
-
-
- <li>
- In the body of the <code>main</code> method, type in
- the following:
- <pre>
-int i=18;
-System.out.println("Hello World");
-</pre>
-
-
- <li>Save this file via <b>File > Save</b>.
-
- <li>
- Run the <code>HelloWorld</code> class: right click
- <b>HelloWorld.java</b> in the <b>Package Explorer</b>
- tab and go <b>Run > Java Application</b>.
-
- <p style="text-align: center"><img border="0"
- width="593"
- height="637"
- src="images/run_java_application.gif"
- alt="running Java Application Dialog"></p>
-
- <p>The result of the execution is printed out in the
- <b>Console</b> tab at the bottom of the page: <i>"Hello
- World!"</i> is printed.</p>
-
- <p style="text-align: center"><img border="0"
- width="456"
- height="290"
- src="images/print_hello_world.gif"
- alt=
- "Result of Application Execution printed out"></p>
-
-
- <li>To close Eclipse<a href="#*">*</a>, go <b>File >
- Exit</b> and then click <b>OK</b>.
- </ol>
-<p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Eclipse_debug_scenario"></a> Debugging an
- Application in Eclipse</h1>
-
- <p>This scenario provides instructions on how to debug a simple
- application in Eclipse<a href="#*">*</a>.</p>
-
- <ol>
- <li>Repeat steps 1 to 11 of the previous scenario to set up
- the workspace and create a new class in the new
- project.
-
- <li>
- Setup the breakpoint. Place the cursor at the following
- line:
- <pre>
-System.out.println ("Hello World!");
-</pre>
-
- <p>Go <b>Run</b> > <b>Toggle Line
- Breakpoint</b>.</p>
-
- <p style="text-align: center"><img border="0"
- width="423"
- height="515"
- src="images/toggle_breakpoint.gif"
- alt=
- "Menu Item for Inserting the Toggle Line Breakpoint"></p>
-
- <p>A blue circle appears on the left border of the
- <b>HelloWorld.java</b> tab.</p>
-
- <p style="text-align: center"><img border="0"
- width="560"
- height="411"
- src="images/selecting_code.gif"
- alt="HelloWorld.java class content selected"></p>
-
-
- <li>Start the debug operation.
- <ol>
- <li> Right-click <b>HelloWorld.java</b> in the <b>Package
- Explorer</b> tab and
- and go <b>Debug As > Debug... </b>. The <strong>Debug</strong> window appears.
- <li>Go to <strong>Java Application</strong> in the left tab and select the <code>HelloWorld</code> application configuration.
- If this configuration is not listed, click <strong>New</strong>. The configuration details of the <code>HelloWord</code> application appear
- on the right side of the workspace.
- <li> Select the<strong> Arguments</strong> pane and type <code>-Xint</code> in the VM arguments field.
- <li>Press the <strong>Debug </strong>button to start the debug operation. You will be prompted to switch to the debug
- perspective. Click <b>Yes</b>.
+ </li>
</ol>
- </ol>
-
- <p style="text-align: center"><img border="0"
- width="601"
- height="614"
- src="images/debug_java_application.gif"
- alt=
- "Menu Item for Debugging a Java Application"></p>
-
- <ol start="4">
- <li>
- The workspace gets updated.
-
- <p>The <b>Debug</b> tab appears in the top right-hand
- corner with the <code>main</code> method selected on
- line 18 in the <code>HelloWorld</code> class. The
- <b>Variables</b> tab also appears with the values of
- local variables <code>i</code> and <code>args</code>. </p>
-
- <p style="text-align: center"><img border="0"
- width="724"
- height="506"
- src="images/debugging_code.gif"
- alt="Code Highlighted"></p>
-
-
- <li>
- To finish the <code>HelloWorld</code> application, go
- <b>Run > Resume<i>.</i></b><br>
- When the application has finished, the <b>Debug</b>
- and the <b>Console</b> tab get updated. The <b>Console</b> tab
- at the bottom displays the result of execution:
- <i>Hello World!</i>
-
- <p style="text-align: center"><img border="0"
- width="725"
- height="574"
- src="images/debug_result.gif"
- alt="Code Highlighted"></p>
-
-
- <li>Close Eclipse<a href="#*">*</a> via <b>File >
- Exit</b> and then click <b>OK</b>.
-</ol>
- <p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Command_line_Options"></a> Supported Command-line
- Options</h1>
-
- <h2><a name="Standard_options"></a>Supported Standard
- Options</h2>
-
- <p>Use the standard supported options listed in this section to
- apply custom configuration settings to your system.</p>
-
- <p><code>-classpath</code> and <code>-cp</code> specify the
- class search path for directories and <code>.zip</code> and
- <code>.jar</code> files.</p>
-
-
- <p class="note">Note</p>
-
- <p class="notetext">Multiple values for directories and
- file locations go in a list separated by the character
- “:” on Linux<a href="#*">*</a> and the
- character “;” on Windows<a href="#*">*</a>.</p>
-
-
- <p><code>-D<name>=<value></code> sets the system
- property to be accessible for the user application through the
- <code>java.lang.System</code> class.</p>
-
- <p><code>-showversion</code> prints the product version and
- continues execution.</p>
-
- <p><code>-version</code> prints the product version and
- exits.</p>
-
- <p><code>-fullversion</code> prints the full product version
- and exits.</p>
-
- <p><code>-verbose [:class|:gc|:jni]</code> enables verbose
- output.</p>
-
- <p><code>-agentlib:<library name>[=<agent
- options>]</code> loads the JVMTI agent library. The library
- name is platform-independent.</p>
-
- <p><code>-agentpath:<library name>[=<agent
- options]</code> loads the JVMTI agent library. The library name
- is platform-dependent.</p>
-
- <p><code>-verify</code> triggers full bytecode verification.
- Minimal verification is performed even without this option
- specified.</p>
-
- <p><code>-?</code> and <code>-help</code> print the help
- message.</p>
-
- <p><code>-X</code> prints help
- information on non-standard options.</p>
-
- <p><code>-jar <jar file></code> specifies the name of the archive containing the class and
- resource files for the application, with the startup class
- indicated in the manifest file.</p>
-
- <h2>Supported Non-Standard Options</h2>
-
- <p>Below supported non-standard options are grouped by their
- functionality.</p>
-
- <h3>Virtual Machine Options</h3>
-
- <p>Use these command-line options to further configure
- DRLVM.</p>
-
- <p class="class">Common Virtual Machine Options</p>
-
- <p><code>-Xbootclasspath:<PATH></code> sets the boot
- class path to the specified value.</p>
-
- <p><code>-Xbootclasspath/a:<PATH></code> appends the
- specified directories and files to the boot class path.</p>
-
- <p><code>-Xbootclasspath/p:<PATH></code> prepends the
- specified directories and files to the boot class path.</p>
-
- <p><code>-Xstats <mask></code> generates various
- statistics.</p>
-
- <p><code>-Xdebug</code> does nothing, is a compatibility
- option.</p>
-
- <p><code>-Xnoagent</code> does nothing, is a compatibility
- option.</p>
-
- <p><code>-Xrun</code> does the same as the
- <code>-agentlib</code> option for backward compatibility with
- JVMDI.</p>
-
- <p><code>-Xverbose[:<category>[:<file>]</code>
- switches on logging for a specified category and logs that
- category to a file.</p>
-
- <p><code>-Xwarn[:<category>[:<file>]</code>
- switches off verbose logging off for a specified category and
- logs that category to a file.</p>
-
- <p><code>-Xverboseconf:<file></code> sets up logging via
- the <code>log4cxx</code> configuration file.</p>
-
- <p><code>-Xverboselog:<file></code> logs verbose output
- to a file.</p>
-
- <p class="class">Memory Heap Options</p>
-
- <p><code>-Xms<size></code> sets the Java<a href=
- "#*">*</a> heap size.</p>
-
- <p><code>-Xmx<size></code> sets the maximum
- Java<a href="#*">*</a> heap size, for example:</p>
- <pre>
--Xms80m
--Xmx60000000</pre>
-
- <p class="class">Logging Options</p>
-
- <p><code>-Xfileline</code> adds source information to logging
- messages.</p>
-
- <p><code>-Xthread</code> adds the thread ID to logging
- messages.</p>
-
- <p><code>-Xcategory</code> adds the category name to logging
- messages.</p>
-
- <p><code>-Xtimestamp</code> adds the timestamp to logging
- messages.</p>
-
- <p><code>-Xfunction</code> adds the function signature to
- logging messages.</p>
- <p><code>-Xlog[:<category>[:<file>]</code> switches on debug logging for a specified category and logs that category to a file. </p>
- <p><code>-Xtrace[:<category>[:<file>]</code> switches on trace logging for a specified category and logs that category to a file. </p>
-
- <p class="class"> Execution Manager Options </p>
- <p> <code>-Xem jet:[<path to JIT library>]</code> runs the virtual machine with a single baseline just-in-time compiler. </p>
- <p> <code>-Xem opt:[<path to JIT library>]</code> runs the virtual machine with a single optimizing just-in-time compiler. </p>
- <p> <code>-verbose:em</code> prints detailed information on execution management. </p>
- <p class="class">Other</p>
-
- <p><code>-Xint</code> enables using the interpreter to execute
- the program.</p>
-
- <p><code>-Xem</code> <code><em options></code> specifies the execution manager specific
- options.</p>
-
- <p><code>-Xdll <dll name></code> indicates a specific
- .dll file.</p>
-
- <p><code>-Xno_parallel_jit</code> prohibits compilation in the
- parallel mode.</p>
-
- <p><code>-Xdumpfile <file></code> specifies the file name
- for the dump.</p>
-
- <h2><a name="JIT_Options"></a> Just-in-time Compiler
- Options</h2>
-
- <p>Use the following command-line options to configure
- operation of the optimizing just-in-time compiler.</p>
-
- <p><code>–Xem opt: -Xjit LOG=\"root=all\"</code> enables
- the single-JIT mode for the optimizing JIT compiler and logs
- all information to <code>stdout</code>.</p>
-
- <p><code>–Xem opt: -Xjit LOG=\"root=ir,file\"</code> does
- the same as above and dumps the intermediate representation
- (IR) logs to file system.</p>
-
- <p><code>–Xem opt: -Xjit LOG=\"filter=file:\"</code>
- generates a list of JIT-compiled methods into the file named
- <code>file</code>.</p>
-
- <p><code>–Xem opt: -Xjit
- LOG=\"opt=ir,file,filter=file:1-3\"</code> dumps the high-level
- representation (HIR) of the first three methods from the file
- <code>file</code> (generated by the previous option).</p>
-
- <p><code>–Xem opt: -Xjit METHODS=\"file:1-3\" -Xjit
- ia32::itrace=on</code> traces, that is, logs to
- <code>stdout</code>, entries and exits to and from the first
- three methods from the file <code>file.</code></p>
-
- <p><code>–Xem opt: -Xjit opt::skip=off –Xjit
- tra::guardedInlining=off</code> enables all high-level
- optimizations and disables translation-time guarded
- inlining.</p>
-
- <p><code>–Xem opt: -Xjit opt::skip=off –Xjit
- tra::guardedInlining=off -Xjit
- LOG=\"root=ir,file,filter=java/lang/Object::\" -Xjit
- opt::dumpdot=on -Xjit ia32::dumpdot=on</code> enables printing
- methods intermediate representations in the form of
- <code>.dot</code> files after major high- and low-level IR
- transformation stages. The resulting <code>.dot</code> files
- can be converted to a graphical representation. With these
- settings, only methods of the <code>Object</code> class are
- logged.</p>
-
- <p class="note">Note</p>
-
- <p class="notetext">General syntax of the JIT log system
- options is the following:</p>
- <pre>
- -Xjit LOG=\"<i>[</i>file<i>|</i>singlefile<i>][</i>filter=<i>filter_expression</i><i>]{<category_name></i> =<i><log_level>}</i>\"
-
+ <h1>
+ Developing Code in Eclipse
+ </h1>
+ <h2>
+ <a id="Eclipse_Hello_world" name="Eclipse_Hello_world"></a> Running an
+ Application in Eclipse
+ </h2>
+ <p>
+ In this section, a simple scenario shows how to create an application
+ and run it in Eclipse<a href="#*">*</a> with our virtual machine.
+ </p>
+ <p class="note">
+ Note
+ </p>
+ <p class="notetext">
+ If you are using Eclipse, see the page <a href="../../documentation/dev_eclipse.html">
+ Working with Harmony Code in
+ Eclipse </a> for specific setup instructions.
+ </p>
+ <p>
+ This scenario provides step-by-step instructions on running a Java
+ application in the Eclipse environment. In the scenario, you will
+ launch Eclipse, create a new project and a new Java class within this
+ project, and finally you will run the new application.
+ </p>
+ <ol start="0">
+ <li>
+ If you have no Eclipse, download the package at <a
+ href="http://download.eclipse.org/eclipse/downloads/"
+ target="_blank">http://download.eclipse.org/eclipse/downloads/</a>,
+ and unpack this distribution.<br />
+ Set up Eclipse as described in <a href="../../documentation/dev_eclipse.html">
+ Working with Harmony Code in Eclipse</a>.
+ </li>
+ <li>
+ Start Eclipse and create a new Java project.
+ </li>
+ <li>
+ In the project workspace, create a <code>HelloWorld</code> class with the
+ <code>public static void main(String[] args)</code> method containing the following code:
+ <pre>
+int i=18;
+System.out.println("Hello, World!");</pre>
+ </li>
+
+ <li>
+ Save the file.
+ </li>
+ <li>
+ Run the <code>HelloWorld</code> class. The result of the execution
+ is printed in the <b>Console</b> tab of your workspace: <i>"Hello,
+ World!"</i> appears.
+ </li>
+ </ol>
+ <h2>
+ <a id="Eclipse_debug_scenario" name="Eclipse_debug_scenario"></a>
+ Debugging an Application in Eclipse
+ </h2>
+ <p>
+ This scenario provides instructions on how to debug a simple
+ application in Eclipse<a href="#*">*</a>.
+ </p>
+ <ol start="0">
+ <li>
+ Repeat steps 0 to 4 of the previous scenario to set up the
+ workspace and create a new class in the new project.
+ </li>
+ <li>
+ Set up breakpoints for debugging purposes, as needed. In the example with the
+ <code>HelloWorld</code> class, set the breakpoint on the following
+ line:
+<pre>
+System.out.println ("Hello, World!");
</pre>
+ </li>
+ <li>
+ Start the debug operation on your class -
+ <code>HelloWorld.java</code> in the example.<br />
+ <br />
+ After the debug run completes, the workspace gets updated with new
+ results.
+ </li>
+ <li>
+ After you are done, resume the application. When the run has
+ completed, the <b>Console</b> tab at the bottom displays the result
+ of execution. In our example, <em>H</em><i>ello World!</i> is
+ printed.
+ </li>
+ </ol>
- <h2><a name="Garbage_Collection_Options"></a>Garbage Collection
- Options</h2>
-
- <p><code>-Xgc fixed runs</code> GC in a non-moving mode.</p>
-
-
- <p class="backtotop"><a href="#TOP">Back to top</a></p>
-
-</body>
+ </body>
</html>
+
</div>
</td>
</tr>
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html?view=diff&rev=479971&r1=479970&r2=479971
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html Tue Nov 28 02:06:12 2006
@@ -13,613 +13,193 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-
+
-->
-
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-
-
-<html>
-<head>
- <meta http-equiv="Content-Type"
- content="text/html; charset=us-ascii">
-
- <title>Getting Started with DRL</title>
- <link rel="Stylesheet"
- type="text/css"
- media="all"
- href="site.css">
-</head>
-
-<body> <h1>
- <a id="Top" name="Top"></a>Getting Started with DRL</h1>
-
- <p>The Dynamic Runtime Layer (DRL) is a clean-room
- implementation of the Java<a href="#*">*</a> 2 Platform,
- Standard Edition (J2SE<a href="#*">*</a>) 1.5.0. The design
- keystones of the DRL virtual machine (VM) are clarity of
- concept, modularity, extensibility, and competitive
- performance. This document describes the first version of DRL
- deployed in March 2006.</p>
-
- <p>To quickly start with DRL, walk through the provided
- scenarios. It is recommended that you strictly follow the
- instructions of this guide to ensure system stability and
- anticipated results.</p>
-
- <p class="TOC"><a href="#Overview">Overview</a></p>
-
- <p class="TOC"><a href="#Before_You_Start">Before You
- Start</a></p>
-
- <p class="TOC"><a href="#Running_Hello">Running an
- Application</a></p>
-
- <p class="TOC"><a href="#Eclipse_Hello_world">Running an
- Application in Eclipse</a></p>
-
- <p class="TOC"><a href="#Eclipse_debug_scenario">Debugging an
- Application in Eclipse</a></p>
-
- <p class="TOC"><a href="#Command_line_Options">Command-line
- Options</a></p>
-
- <h2><a name="Overview"></a>Overview</h2>
-
- <p>In the Getting Started document, the first scenario
- illustrates running an application with DRL, and the two others
- demonstrate running and debugging an application in the
- Eclipse<a href="#*">*</a> integrated development environment.
- DRL is used to run both Eclipse<a href="#*">*</a> and the new
- application. After completing this guide, you will be able to
- run and debug your own applications with DRL.</p>
-
- <h2><a name="Before_You_Start"></a> Before You Start</h2>
-
- <p>By following the instructions in the <code>README.txt</code>
- file, install DRL and run acceptance tests to make sure that
- the installation is complete. You will have the default
- configuration installed on your system. To change the default
- DRL settings, use the <a href=
- "#Command_line_Options">Command-line Options</a>
- listed in this document.</p>
- <h3>Notations Conventions</h3>
- <p>When following the scenarios described below, please make the following adjustments: </p>
- <ul>
- <li>
- In the paths indicated, the slash \ is in the Windows<a href="#*">*</a> style,
- and / is in the Linux<a href="#*">*</a> style. Verify that your paths are correct when doing cut-and-paste.
- <li>The file <code>eclipse.bat</code> on Windows<a href="#*">*</a> corresponds to the file <code>eclipse.sh</code> on Linux<a href="#*">*</a>.
-</ul>
-<p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Running_Hello"></a>Running an Application</h1>
-
- <p>This scenario provides step-by-step instructions on running
- the <code>Hello</code> application in the Windows<a href=
- "#*">*</a> or the Linux<a href=
- "#*">*</a> console. The scenario uses the
- <code>Hello.class</code> Java<a href=
- "#*">*</a> class distributed with the
- product as the sample Java<a href=
- "#*">*</a> application.</p>
-
- <ol>
- <li>To start DRL, change your current directory to the
- <code><<b>installation folder</b>>\bin</code>
- directory.
-
- <li>Check that you have files <code>ij.exe</code> on Windows<a href=
- "#*">*</a> or <code>ij</code> on Linux<a href=
- "#*">*</a> and
- <code>Hello.class</code> in the <code>\bin</code>
- directory.
- <br>
- On Linux<a href="#*">*</a>, make sure that you can run applications
- and load dynamic libraries from the current directory.
- For example:
- <pre>export PATH=.:${PATH}
-export LD_LIBRARY_PATH=${PWD}:${LD_LIBRARY_PATH}</pre>
-
- If you are using the Intel(R) C++ compiler, make sure
- the <code>LD_LIBRARY_PATH</code> contains location of the ICC libraries.
-
- <li>
- Run the <code>Hello</code> application by entering:
- <pre>
-ij Hello
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
+ <title>
+ Getting Started with DRLVM
+ </title>
+ <link rel="Stylesheet" type="text/css" media="all" href="site.css" />
+ </head>
+ <body>
+ <h1>
+ <a id="TOP" name="TOP"></a>Getting Started with DRLVM
+ </h1>
+ <p>
+ The Dynamic Runtime Layer virtual machine (DRLVM) is a clean-room implementation of the
+ Java<a href="#*">*</a> virtual machine for Java 2 Platform, Standard Edition (J2SE<a
+ href="#*">*</a>) 1.5.0. This document gives tips on how to start using
+ the DRL virtual machine (VM). Use this page to learn where to get the
+ code and how to use it. For documentation on the Harmony Java<a
+ href="#*">*</a> class libraries, see the <a
+ href="../classlib/index.html">classlib page</a>.
+ </p>
+ <p>
+ To quickly start with DRL, read this page and follow the instructions.
+ It is recommended that you strictly follow the instructions of this
+ guide to ensure system stability and anticipated results. After
+ completing this guide, you will be able to run and debug your own
+ applications with DRLVM.
+ </p>
+ <h2>
+ <a id="Overview" name="Overview"></a>Overview
+ </h2>
+ <p>
+ For a definition of the DRL virtual machine and links to all docs
+ describing it, see the DRLVM <a href="index.html">component page</a>.
+ For instructions on how to get and build the code, and configure your
+ environment, please visit the <a
+ href="../../quickhelp_users.html">Getting Started for Users</a> page.
+ If you fail to build the source code or come across other problems, go
+ to our project <a href="http://wiki.apache.org/harmony/"
+ target="_blank">Wiki resource</a> and search for your issue on the <a
+ href="http://wiki.apache.org/harmony/DrlvmBuildTroubleshooting"
+ target="_blank">DrlvmBuildTroubleshooting</a> page. If no known issue
+ matches your problem, please write to the mailing list or add your
+ issue to the wiki page.
+ </p>
+ <p>
+ The README file supplied with the source code and the Quick Help
+ instructions enable you to build the VM source code in the default
+ configuration. To modify the code behavior, use the available
+ command-line options, as indicated in the <a
+ href="http://wiki.apache.org/harmony/DrlvmCommandLineOptions"
+ target="_blank">Wiki command-line options page</a>. Read further
+ for illustrations of command-line options usage.
+ </p>
+ <h1>
+ <a id="Running_Hello" name="Running_Hello"></a>Running an Application
+ </h1>
+ <p>
+ This scenario provides step-by-step instructions on running a
+ <code>Hello</code> application in the Windows<a href="#*">*</a> or the
+ Linux<a href="#*">*</a> console. The scenario uses a sample
+ <code>Hello.class</code> Java<a href="#*">*</a> class for illustration.
+ Please use your own application instead.
+ </p>
+ <ol>
+ <li>
+ To start DRL, change your current directory to the
+ <code><<b>installation folder</b>>\bin</code> directory.
+ </li>
+ <li>
+ Check that you have files <code>java.exe</code> on Windows<a
+ href="#*">*</a> or <code>java</code> on Linux<a href="#*">*</a> and
+ <code>Hello.class</code> in the <code>\bin</code> directory.<br />
+ On Linux<a href="#*">*</a>, make sure that you can run
+ applications and load dynamic libraries from the current directory.
+ If you are using the Intel(R) C++ compiler, make sure the
+ <code>LD_LIBRARY_PATH</code> variable contains location of the ICC
+ libraries.
+ </li>
+ <li>
+ Run the <code>Hello</code> application by entering:
+<pre>
+java Hello
</pre>
-
- <p>You will see “<i>Hello World!</i>" printed on
- the screen. This means that you have successfully
- launched the virtual machine, and that
- it has processed the <code>Hello.class</code> Java<a href=
- "#*">*</a>
- class to execute the <code>Hello</code>
- application.</p>
-
- </ol>
-<p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Eclipse_Hello_world"></a> Running an Application
- in Eclipse</h1>
-
- <p>This scenario provides step-by-step instructions on running
- a Java application in the Eclipse<a href="#*">*</a>
- environment. In the scenario, you will launch
- Eclipse<a href="#*">*</a>, create a new project and a new
- Java class within this project, and finally you will run the
- new application.</p>
-
- <ol>
- <li>Download the Eclipse<a href="#*">*</a> 3.1.1 package
- at <a href=
- "http://download.eclipse.org/eclipse/downloads/"
- target=
- "_blank">http://download.eclipse.org/eclipse/downloads/</a>,
- and unpack this distribution.
-
- <li>Set the environment variable <code>ECLIPSE_HOME</code>
- to point to the location of the Eclipse<a href="#*">*</a> installation directory.
- <br>
- On Linux<a href="#*">*</a>,
- if you are using the Intel(R) C++ compiler, additionally set the <code>LD_LIBRARY_PATH</code>
- variable to point to the location of the ICC libraries.
-
- <li>On Windows<a href="#*">*</a>, edit the Eclipse<a href="#*">*</a> launch script
- <code><<b>installation
- folder</b>>/bin/eclipse.bat:</code> make sure
- that <code>BUILD_HOME</code> variable points to the
- <code><<b>installation folder</b>>.
-
- <li>Start Eclipse<a href="#*">*</a> by launching Eclipse starter script:
- <br>on Windows<a href="#*">*</a>:
- <code><<b>installation folder</b>>/bin/eclipse.bat</code>;
- <br>on Linux<a href="#*">*</a>:
- <code><<b>installation folder</b>>/bin/eclipse.sh</code>.
-
- <li>
- After running Eclipse<a href="#*">*</a> starter script, the
- <b>Workspace Launcher</b> dialog opens. Specify the
- path to your workspace directory. In the example, click
- <b>OK</b> to set the default path.
-
- <p style="text-align: center"><img border="0"
- width="438"
- height="244"
- src="images/workspace_launcher.gif"
- alt=
- "Specifying the Workspace directory for the Project"></p>
-
-
- <li>The <b>Welcome</b> page of the Eclipse<a href="#*">*</a>
- environment opens. Close the window to proceed.
-
- <li>
- Create a new project via <b>File > New >
- Project…</b>
-
- <p>The <b>New project</b> dialog appears. Select
- <b>Java Project</b>, click <b>Next</b> and type the
- project name in the <b>New Java Project</b> field, in
- the example, <i>Hello</i>. Then click the <b>Finish</b>
- button.</p>
-
- <p style="text-align: center"><img border="0"
- width="500"
- height="555"
- src="images/new_project.gif"
- alt=
- "Dialog: New Java Project with Default Settings"></p>
-
- <p>When prompted to switch to the Java Perspective,
- click <b>Yes</b>.</p>
-
-
- <li>
- The <b>Package Explorer</b> tab opens in the left-hand
- part of the workspace with the name of your project
- displayed.
-
- <p style="text-align: center"><img border="0"
- width="691"
- height="609"
- src="images/package_explorer.gif"
- alt=
- "Eclipse Platform Workspace with the Package Explorer and the Hello Class">
- </p>
-
-
- <li>
- Create a new class via <b>File > New > Class
- <i>…</i></b>
-
- <p>The <b>New Java Class</b> wizard opens. Type in the
- class name, in the example, <i>HelloWorld</i> and
- select the <b>public static void main(String[]
- args)</b> check box at the bottom of the dialog
- window.</p>
-
- <p style="text-align: center"><img border="0"
- width="515"
- height="557"
- src="images/new_java_class.gif"
- alt=
- "Dialog New Java Class with Settings Configured as Required">
+ <p>
+ You will see “<i>Hello World!</i>" printed on the screen.
+ This means that you have successfully launched the virtual
+ machine, and that it has processed the <code>Hello.class</code>
+ Java<a href="#*">*</a> class to execute the <code>Hello</code>
+ application.
</p>
-
-
- <li>
- You have created the <code>HelloWorld</code> class. The
- workspace gets updated with the class information as
- shown below.
-
- <p>In the <b>Package Explorer</b> window, you can see
- that the class is in the default package. The
- <b>Outline</b> window displays the one method of this
- class: the <code>main</code> method with an array of
- <code>String</code> parameters.</p>
-
- <p style="text-align: center"><img border="0"
- width="834"
- height="636"
- src="images/workspace1.gif"
- alt=
- "Workspace with the HelloWorld.java Class conent Displayed">
- </p>
-
-
- <li>
- In the body of the <code>main</code> method, type in
- the following:
- <pre>
-int i=18;
-System.out.println("Hello World");
-</pre>
-
-
- <li>Save this file via <b>File > Save</b>.
-
- <li>
- Run the <code>HelloWorld</code> class: right click
- <b>HelloWorld.java</b> in the <b>Package Explorer</b>
- tab and go <b>Run > Java Application</b>.
-
- <p style="text-align: center"><img border="0"
- width="593"
- height="637"
- src="images/run_java_application.gif"
- alt="running Java Application Dialog"></p>
-
- <p>The result of the execution is printed out in the
- <b>Console</b> tab at the bottom of the page: <i>"Hello
- World!"</i> is printed.</p>
-
- <p style="text-align: center"><img border="0"
- width="456"
- height="290"
- src="images/print_hello_world.gif"
- alt=
- "Result of Application Execution printed out"></p>
-
-
- <li>To close Eclipse<a href="#*">*</a>, go <b>File >
- Exit</b> and then click <b>OK</b>.
- </ol>
-<p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Eclipse_debug_scenario"></a> Debugging an
- Application in Eclipse</h1>
-
- <p>This scenario provides instructions on how to debug a simple
- application in Eclipse<a href="#*">*</a>.</p>
-
- <ol>
- <li>Repeat steps 1 to 11 of the previous scenario to set up
- the workspace and create a new class in the new
- project.
-
- <li>
- Setup the breakpoint. Place the cursor at the following
- line:
- <pre>
-System.out.println ("Hello World!");
-</pre>
-
- <p>Go <b>Run</b> > <b>Toggle Line
- Breakpoint</b>.</p>
-
- <p style="text-align: center"><img border="0"
- width="423"
- height="515"
- src="images/toggle_breakpoint.gif"
- alt=
- "Menu Item for Inserting the Toggle Line Breakpoint"></p>
-
- <p>A blue circle appears on the left border of the
- <b>HelloWorld.java</b> tab.</p>
-
- <p style="text-align: center"><img border="0"
- width="560"
- height="411"
- src="images/selecting_code.gif"
- alt="HelloWorld.java class content selected"></p>
-
-
- <li>Start the debug operation.
- <ol>
- <li> Right-click <b>HelloWorld.java</b> in the <b>Package
- Explorer</b> tab and
- and go <b>Debug As > Debug... </b>. The <strong>Debug</strong> window appears.
- <li>Go to <strong>Java Application</strong> in the left tab and select the <code>HelloWorld</code> application configuration.
- If this configuration is not listed, click <strong>New</strong>. The configuration details of the <code>HelloWord</code> application appear
- on the right side of the workspace.
- <li> Select the<strong> Arguments</strong> pane and type <code>-Xint</code> in the VM arguments field.
- <li>Press the <strong>Debug </strong>button to start the debug operation. You will be prompted to switch to the debug
- perspective. Click <b>Yes</b>.
+ </li>
</ol>
- </ol>
-
- <p style="text-align: center"><img border="0"
- width="601"
- height="614"
- src="images/debug_java_application.gif"
- alt=
- "Menu Item for Debugging a Java Application"></p>
-
- <ol start="4">
- <li>
- The workspace gets updated.
-
- <p>The <b>Debug</b> tab appears in the top right-hand
- corner with the <code>main</code> method selected on
- line 18 in the <code>HelloWorld</code> class. The
- <b>Variables</b> tab also appears with the values of
- local variables <code>i</code> and <code>args</code>. </p>
-
- <p style="text-align: center"><img border="0"
- width="724"
- height="506"
- src="images/debugging_code.gif"
- alt="Code Highlighted"></p>
-
-
- <li>
- To finish the <code>HelloWorld</code> application, go
- <b>Run > Resume<i>.</i></b><br>
- When the application has finished, the <b>Debug</b>
- and the <b>Console</b> tab get updated. The <b>Console</b> tab
- at the bottom displays the result of execution:
- <i>Hello World!</i>
-
- <p style="text-align: center"><img border="0"
- width="725"
- height="574"
- src="images/debug_result.gif"
- alt="Code Highlighted"></p>
-
-
- <li>Close Eclipse<a href="#*">*</a> via <b>File >
- Exit</b> and then click <b>OK</b>.
-</ol>
- <p class="backtotop"><a href="#TOP">Back to top</a></p>
- <h1><a name="Command_line_Options"></a> Supported Command-line
- Options</h1>
-
- <h2><a name="Standard_options"></a>Supported Standard
- Options</h2>
-
- <p>Use the standard supported options listed in this section to
- apply custom configuration settings to your system.</p>
-
- <p><code>-classpath</code> and <code>-cp</code> specify the
- class search path for directories and <code>.zip</code> and
- <code>.jar</code> files.</p>
-
-
- <p class="note">Note</p>
-
- <p class="notetext">Multiple values for directories and
- file locations go in a list separated by the character
- “:” on Linux<a href="#*">*</a> and the
- character “;” on Windows<a href="#*">*</a>.</p>
-
-
- <p><code>-D<name>=<value></code> sets the system
- property to be accessible for the user application through the
- <code>java.lang.System</code> class.</p>
-
- <p><code>-showversion</code> prints the product version and
- continues execution.</p>
-
- <p><code>-version</code> prints the product version and
- exits.</p>
-
- <p><code>-fullversion</code> prints the full product version
- and exits.</p>
-
- <p><code>-verbose [:class|:gc|:jni]</code> enables verbose
- output.</p>
-
- <p><code>-agentlib:<library name>[=<agent
- options>]</code> loads the JVMTI agent library. The library
- name is platform-independent.</p>
-
- <p><code>-agentpath:<library name>[=<agent
- options]</code> loads the JVMTI agent library. The library name
- is platform-dependent.</p>
-
- <p><code>-verify</code> triggers full bytecode verification.
- Minimal verification is performed even without this option
- specified.</p>
-
- <p><code>-?</code> and <code>-help</code> print the help
- message.</p>
-
- <p><code>-X</code> prints help
- information on non-standard options.</p>
-
- <p><code>-jar <jar file></code> specifies the name of the archive containing the class and
- resource files for the application, with the startup class
- indicated in the manifest file.</p>
-
- <h2>Supported Non-Standard Options</h2>
-
- <p>Below supported non-standard options are grouped by their
- functionality.</p>
-
- <h3>Virtual Machine Options</h3>
-
- <p>Use these command-line options to further configure
- DRLVM.</p>
-
- <p class="class">Common Virtual Machine Options</p>
-
- <p><code>-Xbootclasspath:<PATH></code> sets the boot
- class path to the specified value.</p>
-
- <p><code>-Xbootclasspath/a:<PATH></code> appends the
- specified directories and files to the boot class path.</p>
-
- <p><code>-Xbootclasspath/p:<PATH></code> prepends the
- specified directories and files to the boot class path.</p>
-
- <p><code>-Xstats <mask></code> generates various
- statistics.</p>
-
- <p><code>-Xdebug</code> does nothing, is a compatibility
- option.</p>
-
- <p><code>-Xnoagent</code> does nothing, is a compatibility
- option.</p>
-
- <p><code>-Xrun</code> does the same as the
- <code>-agentlib</code> option for backward compatibility with
- JVMDI.</p>
-
- <p><code>-Xverbose[:<category>[:<file>]</code>
- switches on logging for a specified category and logs that
- category to a file.</p>
-
- <p><code>-Xwarn[:<category>[:<file>]</code>
- switches off verbose logging off for a specified category and
- logs that category to a file.</p>
-
- <p><code>-Xverboseconf:<file></code> sets up logging via
- the <code>log4cxx</code> configuration file.</p>
-
- <p><code>-Xverboselog:<file></code> logs verbose output
- to a file.</p>
-
- <p class="class">Memory Heap Options</p>
-
- <p><code>-Xms<size></code> sets the Java<a href=
- "#*">*</a> heap size.</p>
-
- <p><code>-Xmx<size></code> sets the maximum
- Java<a href="#*">*</a> heap size, for example:</p>
- <pre>
--Xms80m
--Xmx60000000</pre>
-
- <p class="class">Logging Options</p>
-
- <p><code>-Xfileline</code> adds source information to logging
- messages.</p>
-
- <p><code>-Xthread</code> adds the thread ID to logging
- messages.</p>
-
- <p><code>-Xcategory</code> adds the category name to logging
- messages.</p>
-
- <p><code>-Xtimestamp</code> adds the timestamp to logging
- messages.</p>
-
- <p><code>-Xfunction</code> adds the function signature to
- logging messages.</p>
- <p><code>-Xlog[:<category>[:<file>]</code> switches on debug logging for a specified category and logs that category to a file. </p>
- <p><code>-Xtrace[:<category>[:<file>]</code> switches on trace logging for a specified category and logs that category to a file. </p>
-
- <p class="class"> Execution Manager Options </p>
- <p> <code>-Xem jet:[<path to JIT library>]</code> runs the virtual machine with a single baseline just-in-time compiler. </p>
- <p> <code>-Xem opt:[<path to JIT library>]</code> runs the virtual machine with a single optimizing just-in-time compiler. </p>
- <p> <code>-verbose:em</code> prints detailed information on execution management. </p>
- <p class="class">Other</p>
-
- <p><code>-Xint</code> enables using the interpreter to execute
- the program.</p>
-
- <p><code>-Xem</code> <code><em options></code> specifies the execution manager specific
- options.</p>
-
- <p><code>-Xdll <dll name></code> indicates a specific
- .dll file.</p>
-
- <p><code>-Xno_parallel_jit</code> prohibits compilation in the
- parallel mode.</p>
-
- <p><code>-Xdumpfile <file></code> specifies the file name
- for the dump.</p>
-
- <h2><a name="JIT_Options"></a> Just-in-time Compiler
- Options</h2>
-
- <p>Use the following command-line options to configure
- operation of the optimizing just-in-time compiler.</p>
-
- <p><code>–Xem opt: -Xjit LOG=\"root=all\"</code> enables
- the single-JIT mode for the optimizing JIT compiler and logs
- all information to <code>stdout</code>.</p>
-
- <p><code>–Xem opt: -Xjit LOG=\"root=ir,file\"</code> does
- the same as above and dumps the intermediate representation
- (IR) logs to file system.</p>
-
- <p><code>–Xem opt: -Xjit LOG=\"filter=file:\"</code>
- generates a list of JIT-compiled methods into the file named
- <code>file</code>.</p>
-
- <p><code>–Xem opt: -Xjit
- LOG=\"opt=ir,file,filter=file:1-3\"</code> dumps the high-level
- representation (HIR) of the first three methods from the file
- <code>file</code> (generated by the previous option).</p>
-
- <p><code>–Xem opt: -Xjit METHODS=\"file:1-3\" -Xjit
- ia32::itrace=on</code> traces, that is, logs to
- <code>stdout</code>, entries and exits to and from the first
- three methods from the file <code>file.</code></p>
-
- <p><code>–Xem opt: -Xjit opt::skip=off –Xjit
- tra::guardedInlining=off</code> enables all high-level
- optimizations and disables translation-time guarded
- inlining.</p>
-
- <p><code>–Xem opt: -Xjit opt::skip=off –Xjit
- tra::guardedInlining=off -Xjit
- LOG=\"root=ir,file,filter=java/lang/Object::\" -Xjit
- opt::dumpdot=on -Xjit ia32::dumpdot=on</code> enables printing
- methods intermediate representations in the form of
- <code>.dot</code> files after major high- and low-level IR
- transformation stages. The resulting <code>.dot</code> files
- can be converted to a graphical representation. With these
- settings, only methods of the <code>Object</code> class are
- logged.</p>
-
- <p class="note">Note</p>
-
- <p class="notetext">General syntax of the JIT log system
- options is the following:</p>
- <pre>
- -Xjit LOG=\"<i>[</i>file<i>|</i>singlefile<i>][</i>filter=<i>filter_expression</i><i>]{<category_name></i> =<i><log_level>}</i>\"
-
+ <h1>
+ Developing Code in Eclipse
+ </h1>
+ <h2>
+ <a id="Eclipse_Hello_world" name="Eclipse_Hello_world"></a> Running an
+ Application in Eclipse
+ </h2>
+ <p>
+ In this section, a simple scenario shows how to create an application
+ and run it in Eclipse<a href="#*">*</a> with our virtual machine.
+ </p>
+ <p class="note">
+ Note
+ </p>
+ <p class="notetext">
+ If you are using Eclipse, see the page <a href="../../documentation/dev_eclipse.html">
+ Working with Harmony Code in
+ Eclipse </a> for specific setup instructions.
+ </p>
+ <p>
+ This scenario provides step-by-step instructions on running a Java
+ application in the Eclipse environment. In the scenario, you will
+ launch Eclipse, create a new project and a new Java class within this
+ project, and finally you will run the new application.
+ </p>
+ <ol start="0">
+ <li>
+ If you have no Eclipse, download the package at <a
+ href="http://download.eclipse.org/eclipse/downloads/"
+ target="_blank">http://download.eclipse.org/eclipse/downloads/</a>,
+ and unpack this distribution.<br />
+ Set up Eclipse as described in <a href="../../documentation/dev_eclipse.html">
+ Working with Harmony Code in Eclipse</a>.
+ </li>
+ <li>
+ Start Eclipse and create a new Java project.
+ </li>
+ <li>
+ In the project workspace, create a <code>HelloWorld</code> class with the
+ <code>public static void main(String[] args)</code> method containing the following code:
+ <pre>
+int i=18;
+System.out.println("Hello, World!");</pre>
+ </li>
+
+ <li>
+ Save the file.
+ </li>
+ <li>
+ Run the <code>HelloWorld</code> class. The result of the execution
+ is printed in the <b>Console</b> tab of your workspace: <i>"Hello,
+ World!"</i> appears.
+ </li>
+ </ol>
+ <h2>
+ <a id="Eclipse_debug_scenario" name="Eclipse_debug_scenario"></a>
+ Debugging an Application in Eclipse
+ </h2>
+ <p>
+ This scenario provides instructions on how to debug a simple
+ application in Eclipse<a href="#*">*</a>.
+ </p>
+ <ol start="0">
+ <li>
+ Repeat steps 0 to 4 of the previous scenario to set up the
+ workspace and create a new class in the new project.
+ </li>
+ <li>
+ Set up breakpoints for debugging purposes, as needed. In the example with the
+ <code>HelloWorld</code> class, set the breakpoint on the following
+ line:
+<pre>
+System.out.println ("Hello, World!");
</pre>
+ </li>
+ <li>
+ Start the debug operation on your class -
+ <code>HelloWorld.java</code> in the example.<br />
+ <br />
+ After the debug run completes, the workspace gets updated with new
+ results.
+ </li>
+ <li>
+ After you are done, resume the application. When the run has
+ completed, the <b>Console</b> tab at the bottom displays the result
+ of execution. In our example, <em>H</em><i>ello World!</i> is
+ printed.
+ </li>
+ </ol>
- <h2><a name="Garbage_Collection_Options"></a>Garbage Collection
- Options</h2>
-
- <p><code>-Xgc fixed runs</code> GC in a non-moving mode.</p>
-
-
- <p class="backtotop"><a href="#TOP">Back to top</a></p>
-
-</body>
+ </body>
</html>
+
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/getting_started.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/getting_started.xml?view=diff&rev=479971&r1=479970&r2=479971
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/getting_started.xml (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/getting_started.xml Tue Nov 28 02:06:12 2006
@@ -20,7 +20,7 @@
<document>
<properties>
- <title>Getting Started</title>
+ <title>Getting Started with DRLVM</title>
<author email="dev@harmony.apache.org">Harmony Documentation Team</author>
</properties>
[general] log messages (was: Re: svn commit: r479971 - in /harmony/standard/site:
docs/subcomponents/drlvm/getting_started.html xdocs/subcomponents/drlvm/GettingStarted.html
xdocs/subcomponents/drlvm/getting_started.xml)
Posted by Tim Ellison <t....@gmail.com>.
nadinem@apache.org wrote:
> Author: nadinem
> Date: Tue Nov 28 02:06:12 2006
> New Revision: 479971
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=479971
> Log:
> Resolve H-2150: remove old/redundant info and screenshots
>
> Modified:
> harmony/standard/site/docs/subcomponents/drlvm/getting_started.html
> harmony/standard/site/xdocs/subcomponents/drlvm/GettingStarted.html
> harmony/standard/site/xdocs/subcomponents/drlvm/getting_started.xml
Nadya, if you spell out the issue name in full, i.e. HARMONY-2150 then
JIRA will link together the commit with the issue and we can see the
full life-cycle together. It can't do that if you abbreviate it to 'H'.
Regards,
Tim
--
Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.