With NADK, a variety of WAD files can be created easily by specifying options when executing make. These options are described below.
Define the option NANDAPP to build the application as a NAND application and create a WAD file. Either specify this option at build time when creating the NAND application or define the NANDAPP macro in the source before including revolution/cnt.h.
If target WAD files have not been specified, then WAD files are created from all ELF files. To create a WAD file for a specific application only, specify a target name as shown below.
The following command is used to build the application xxxxD.elf as a NAND application and create a WAD file.
|
When NANDAPP is defined as an option, WAD files are created at the same time that the NAND application is built. However, if NOEXPORT is also defined as an option, then the NAND application will be built, but no WAD files will be created (that is, only ELF files will be created).
When NANDAPP is defined as an option, the application is built as a NAND application and WAD files are created, but the program is compressed at this time by default. If NOCOMPRESS is also defined at the same time, the program is not compressed.
As the default, an ELF file with the same name as the WAD file is created as the application. WAD_APP allows you to specify the application when creating a WAD file. Be sure this is not a WAD file name.
Remember to add D to the name of the WAD file for debug versions; for the release version, remember to set NDEBUG=TRUE.If you forget to do this, an error message will be output saying that there is no target.
The following is the command for creating the WAD file named xxxxD.wad with yyyy specified as the application:
|
This allows you to specify the archive file(s) to be made into content files. When specifying multiple files, be sure to delimit using a comma. (If a target name is not specified, the specified content files are packaged with every ELF file when WAD files are created). Do not use a space to separate the specified files. Be aware that when specifying these files, an absolute path beginning with /cygdrive/c/ cannot be used. Use Windows paths that begin with C:/ to use absolute paths.
The following command specifies cnt/zzzz.arc (located under the directory in which make is being executed) as the content file for xxxxD.wad.
|
This collects the contents of the dvddata/content{x} directory, with x being the number specified with CNT_IDX, into an archive and packages it into the WAD file. When specifying multiple directories, use a comma as the delimiter. When CNT_IDX is specified, the specified directory is always collected into an archive. When CNT_ARG is specified at the same time, the file specified by CNT_ARG is placed after the contents specified by CNT_IDX.
The following command is used to create xxxxD.wad using the contents of /dvddata/content2/ as content file 2 and the contents of /dvddata/content3/ as content file 3.
|
This allows you to specify the options that are passed to makeWad.exe. Enclose the specifications with double quotation marks. See makeWad for details on the makeWad options.
The example below shows how you would set the game code to "XXXX" (0x58585858):
|
2008/02/15 Added mention that NAND applications can also be created by directly defining NANDAPP in the source.
2008/01/11 Added the NOCOMPRESS option.
2007/11/20 Standardized the use of the term "content file".
2007/07/18 Added the NOEXPORT option.
2006/09/15 Revised the command examples.
2006/08/15 Initial version.
CONFIDENTIAL