1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html>
3
4<head>
5<META http-equiv="Content-Type" content="text/html; charset=windows-1252">
6<META name="GENERATOR" content="Microsoft FrontPage 5.0">
7<META http-equiv="Content-Style-Type" content="text/css">
8<LINK rel="stylesheet" type="text/css" href="../../CSS/revolution.css">
9<title>GD Demos</title>
10</head>
11
12<body>
13
14<h1>Graphics Display List (GD) Sample Demos</h1>
15
16<h2>Location</h2>
17<p><CODE>$REVOLUTION_SDK_ROOT/build/demos/gddemo</CODE></p>
18
19<h2>Compilation</h2>
20<p>Change directories to <CODE>$REVOLUTION_SDK_ROOT/build/demos/gddemo</CODE> and enter <CODE>make</CODE>. The executable programs (<CODE>.elf</CODE> files) will be generated under <CODE>$REVOLUTION_SDK_ROOT/build/demos/gddemo/bin/RVL/</CODE>.</p>
21
22<h2>Execution</h2>
23<p>Before executing a program, you must configure <CODE>DVDRoot</CODE>. Copy the <CODE>$REVOLUTION_SDK_ROOT/dvddata</CODE> directory to the emulation hard disk drive, and then specify the directory as <CODE>DVDRoot</CODE>.</p>
24<p>Change directories to <CODE>$REVOLUTION_SDK_ROOT/build/demos/gddemo/bin/RVL/</CODE> and take one of the following actions:</p>
25<ul>
26<li>?To simply run the application, run the <code>ndrun</code> script, using the <code>.elf</code> file as an argument</li>
27<li>?If you want to debug with CodeWarrior, run <CODE>ide</CODE> with the <code>.elf</code> file as an argument.</li>
28</ul>
29<p>For each of these sample programs, there are two <CODE>.elf</CODE> files (Revolution executables) and one host PC executable. (Microsoft Visual Studio .NET 2003 or later is required to build executables on the host PC). Workspace and project files are contained in the vc++ subdirectory.</p>
30
31<h2>Description</h2>
32<TABLE class="demo_list" border="1">
33    <tr>
34<th nowrap>gd-texture-gc-create<br> gd-texture-gc-load</th>
35<td>Display list sample with texture state.</td>
36  </tr>
37    <tr>
38<th nowrap>gd-matrix-gc-create<br> gd-matrix-gc-load</th>
39<td>Display list sample with transform matrices.</td>
40  </tr>
41    <tr>
42<th nowrap>gd-light-gc-create<br> gd-light-gc-load</th>
43<td>Display list sample with lighting state.</td>
44  </tr>
45    <tr>
46<th nowrap>gd-tev-gc-create<br> gd-tev-gc-load</th>
47<td>Display list sample with multitexturing shader commands.</td>
48  </tr>
49    <TR>
50<th nowrap>gd-indtex-gc-create<br> gd-indtex-gc-load</th>
51<TD>Display list sample with indirect texturing commands.</TD>
52    </TR>
53    <tr>
54<th nowrap>gd-init-gc-create<br> gd-init-gc-load</th>
55<td>Display list sample for state initialization.</td>
56  </tr>
57</table>
58
59<p>The first sample <CODE>.elf</CODE> file (with a name like <CODE>gd-*-gc-create.elf</CODE>) creates display lists during runtime (prior to the first frame of execution) and uses them to render objects.</p>
60<p>The second sample (with a name like <CODE>gd-*-gc-load.elf</CODE>) has basically the same behavior as the first sample; however, this sample loads pregenerated display lists from a file instead of creating them during runtime.</p>
61<p>The host PC executable (with a name like <CODE>gd-*-host.exe</CODE>) creates display lists offline and outputs a file that is loaded by the sample mentioned above. This program calls the same code as the runtime demo for creating a display list (see <CODE>gd-*-create.c</CODE>).</p>
62
63<h2>See Also</h2>
64<P class="reference">
65<a href="../toc.html" target="contents">GD API</a>
66</p>
67
68<H2>Revision History</H2>
69<P>
702006/03/01 Initial version.<BR>
71</P>
72
73<hr><p>CONFIDENTIAL</p></body>
74</html>