$REVOLUTION_SDK_ROOT/build/demos/gddemo
Change directories to $REVOLUTION_SDK_ROOT/build/demos/gddemo and enter make. The executable programs (.elf files) will be generated under $REVOLUTION_SDK_ROOT/build/demos/gddemo/bin/RVL/.
Before executing a program, you must configure DVDRoot. Copy the $REVOLUTION_SDK_ROOT/dvddata directory to the emulation hard disk drive, and then specify the directory as DVDRoot.
Change directories to $REVOLUTION_SDK_ROOT/build/demos/gddemo/bin/RVL/ and take one of the following actions:
ndrun script using a .elf file as an argument.ide with an .elf file as an argument to debug using CodeWarrior.For each of these demos, there are two .elf 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.
gd-texture-gc-create |
Display list sample with texture state. |
gd-matrix-gc-create |
Display list sample with transform matrices. |
gd-light-gc-create |
Display list sample with lighting state. |
gd-tev-gc-create |
Display list sample with multitexturing shader commands. |
gd-indtex-gc-create |
Display list sample with indirect texturing commands. |
gd-init-gc-create |
Display list sample for state initialization. |
The first demo .elf file (with a name like gd-*-gc-create.elf) creates display lists during runtime (prior to the first frame of execution) and uses them to render objects.
The second demo (with a name like gd-*-gc-load.elf) has basically the same behavior as the first demo; however, this demo loads pregenerated display lists from a file instead of creating them during runtime.
The host PC executable (with a name like gd-*-host.exe) creates display lists offline and outputs a file that is loaded by the demo mentioned above. This program calls the same code as the runtime demo for creating a display list (see gd-*-create.c).
03/01/2006 Initial version.