1<html> 2<head> 3<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> 4<LINK rel="stylesheet" type="text/css" href="../../CSS/revolution.css"> 5<base target="main"> 6<title>make Command Options</title> 7</head> 8 9<body> 10 11<h1>make Command Options</h1> 12<p> 13With NADK, a variety of WAD files can be created easily by specifying options when executing <CODE>make</CODE>. These options are described below. 14</p> 15 16<h2>Command Options</h2> 17<H3>1. NANDAPP</H3> 18<p> 19Define the option <CODE>NANDAPP</CODE> 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 <CODE>NANDAPP</CODE> macro in the source before including <code>revolution/cnt.h</code>.<br>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.<br><br>The following command is used to build the application <CODE>xxxxD.elf</CODE> as a NAND application and create a WAD file.</p> 20<TABLE border="1" width="100%"> 21 <TBODY> 22 <TR> 23 <TD width="100%"> 24 <PRE><CODE> 25% make xxxxD.wad NANDAPP=TRUE</CODE></PRE> 26 </TD> 27 </TR> 28 </TBODY> 29</TABLE> 30 31 32<H3>2. NOEXPORT</H3> 33<p> 34When <CODE>NANDAPP</CODE> is defined as an option, WAD files are created at the same time that the NAND application is built. However, if <CODE>NOEXPORT</CODE> 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). 35</p> 36 37<H3>3. NOCOMPRESS</H3> 38<p> 39When <CODE>NANDAPP</CODE> 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 <CODE>NOCOMPRESS</CODE> is also defined at the same time, the program is not compressed. 40</p> 41 42 43<H3>4. WAD_APP</H3> 44<p> 45As the default, an ELF file with the same name as the WAD file is created as the application. <CODE>WAD_APP</CODE> allows you to specify the application when creating a WAD file. Be sure this is not a WAD file name.<br><b><font color=red>Remember to add <CODE>D</CODE> to the name of the WAD file for debug versions; for the release version, remember to set <CODE>NDEBUG=TRUE</CODE>.</font>If you forget to do this, an error message will be output saying that there is no target. </b><br><br> The following is the command for creating the WAD file named <CODE>xxxxD.wad</CODE> with <CODE>yyyy</CODE> specified as the application:</p> 46<TABLE border="1" width="100%"> 47 <TBODY> 48 <TR> 49 <TD width="100%"> 50 <PRE><CODE> 51% make xxxxD.wad NANDAPP=TRUE WAD_APP=yyyy</CODE></PRE> 52 </TD> 53 </TR> 54 </TBODY> 55</TABLE> 56 57<H3>5. CNT_ARG</H3> 58<p> 59This 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 <CODE>/cygdrive/c/</CODE> cannot be used. Use Windows paths that begin with <CODE>C:/</CODE> to use absolute paths. <br><br> The following command specifies <CODE>cnt/zzzz.arc</CODE> (located under the directory in which <CODE>make</CODE> is being executed) as the content file for <CODE>xxxxD.wad</CODE>.</p> 60<TABLE border="1" width="100%"> 61 <TBODY> 62 <TR> 63 <TD width="100%"> 64 <PRE><CODE> 65% make xxxxD.wad NANDAPP=TRUE CNT_ARG=cnt/zzzz.arc</CODE></PRE> 66 </TD> 67 </TR> 68 </TBODY> 69</TABLE> 70 71<H3>6. CNT_IDX</H3> 72<p> 73This collects the contents of the <CODE>dvddata/content{x}</CODE> directory, with <CODE>x</CODE> being the number specified with <CODE>CNT_IDX</CODE>, into an archive and packages it into the <CODE>WAD</CODE> file. When specifying multiple directories, use a comma as the delimiter. When <CODE>CNT_IDX</CODE> is specified, the specified directory is always collected into an archive. When <CODE>CNT_ARG</CODE> is specified at the same time, the file specified by <CODE>CNT_ARG</CODE> is placed after the contents specified by <CODE>CNT_IDX</CODE>. <br><br>The following command is used to create <CODE>xxxxD.wad</CODE> using the contents of <CODE>/dvddata/content2/</CODE> as content file 2 and the contents of <CODE>/dvddata/content3/</CODE> as content file 3. 74</p> 75<TABLE border="1" width="100%"> 76 <TBODY> 77 <TR> 78 <TD width="100%"> 79 <PRE><CODE> 80% make xxxxD.wad NANDAPP=TRUE CNT_IDX=2,3</CODE></PRE> 81 </TD> 82 </TR> 83 </TBODY> 84</TABLE> 85 86<H3>7. WAD_OPTION</H3> 87<p> 88This allows you to specify the options that are passed to <CODE>makeWad.exe</CODE>. Enclose the specifications with double quotation marks. See <a href="./makeWad.html"><CODE>makeWad</CODE></a> for details on the <CODE>makeWad</CODE> options.<br><br>The example below shows how you would set the game code to "XXXX" (<CODE>0x58585858</CODE>):</p> 89<TABLE border="1" width="100%"> 90 <TBODY> 91 <TR> 92 <TD width="100%"> 93 <PRE><CODE> 94% make xxxxD.wad NANDAPP=TRUE WAD_OPTION="-gc 0x58585858"</CODE></PRE> 95 </TD> 96 </TR> 97 </TBODY> 98</TABLE> 99 100<h2>Revision History</h2> 101<p> 1022008/02/15 Added mention that NAND applications can also be created by directly defining <CODE>NANDAPP</CODE> in the source.<br>2008/01/11 Added the <CODE>NOCOMPRESS</CODE> option.<br>2007/11/20 Standardized the use of the term "content file".<BR>2007/07/18 Added the <CODE>NOEXPORT</CODE> option.<br>2006/09/15 Revised the command examples.<br>2006/08/15 Initial version.</p> 103 104 105<hr><p>CONFIDENTIAL</p></body> 106</html> 107