1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-5986717C-C777-590D-8487-CB8ED488E975" xml:lang="en"><title>makmake

    13 command syntax</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p>Symbian projects are defined by an <filepath>.mmp</filepath> file which

    15 specifies the essential elements of the project. The <filepath>makmake</filepath> tool

    16 then uses this environment neutral file to build makefiles for use in various

    17 environments. These makefiles are then used for project development. </p>

    18 <p><b>Invocation syntax </b> </p>

    19 <p> <codeph>makmake</codeph> [ <varname>options</varname> ] [ <varname>source-path</varname> ] <varname>project</varname> <varname>platform</varname>  </p>

    20 <p>Details of <varname>options</varname>, <varname>source-path</varname>, <varname>project</varname>,

    21 and <varname>platform</varname> are given below. </p>

    22 <p><b>Options </b> </p>

    23 <table id="GUID-BDAF523E-3992-5F10-9509-101F41F14CCF">

    24 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>

    25 <tbody>

    26 <row>

    27 <entry><p> <codeph> -d</codeph>  </p> </entry>

    28 <entry><p>Indicates that the makefile is to be created in directory <filepath>epoc32\build\</filepath> <varname>path_to_mmp_file</varname> <filepath>\</filepath> <codeph>mmp_basename</codeph> <filepath>\</filepath> <varname>platform</varname> rather

    29 than the directory in which <filepath>makmake</filepath> was invoked. </p> <p>Note

    30 that relative paths within the created makefile will be relative to the directory

    31 in which <filepath>makmake </filepath> was invoked so <filepath>nmake</filepath> should

    32 be invoked from that directory too if the project is to build correctly. </p> </entry>

    33 </row>

    34 <row>

    35 <entry><p> <codeph> -v</codeph>  </p> </entry>

    36 <entry><p>Indicates verbose operation </p> <p>When this flag is specified, <filepath>makmake</filepath> prints

    37 many progress messages. The default is to give error messages only. </p> </entry>

    38 </row>

    39 <row>

    40 <entry><p> <codeph> -mmp</codeph>  </p> </entry>

    41 <entry><p>Provides basic syntax guide to writing <filepath>.mmp</filepath> files

    42 instead of making the makefile. </p> </entry>

    43 </row>

    44 <row>

    45 <entry><p> <codeph> -plat </codeph>  <varname>platform</varname>  </p> </entry>

    46 <entry><p>Provides syntax guide to writing platform-specific sections of <filepath>.mmp</filepath> files,

    47 and information about which macros are defined for preprocessing the <filepath>.mmp</filepath> files. </p> </entry>

    48 </row>

    49 <row>

    50 <entry><p> <codeph>-arm</codeph>  </p> </entry>

    51 <entry><p>Instructs an ARMV5 build to not build the project as THUMB, but

    52 as the appropriate ARM ABI. </p> <p>For details, see <xref href="GUID-EFF3BD37-BC29-52F5-B8AA-6362F0C3E20F.dita">ARMV5

    53 build target</xref>. </p> </entry>

    54 </row>

    55 <row>

    56 <entry><p> <codeph>-debug</codeph>  </p> </entry>

    57 <entry><p>Generates symbolic debug information for release or debug builds. </p> </entry>

    58 </row>

    59 <row>

    60 <entry><p> <codeph>-no_debug</codeph>  </p> </entry>

    61 <entry><p>Does not generate symbolic debug information for release or debug

    62 builds. </p> </entry>

    63 </row>

    64 </tbody>

    65 </tgroup>

    66 </table>

    67 <p>Note that you can either use <codeph>-debug</codeph> to generate or <codeph>-no_debug</codeph> to

    68 not generate the symbolic debug information, irrespective of <codeph>UREL</codeph> or <codeph>UDEB</codeph> build. </p>

    69 <p><b>source-path </b> </p>

    70 <p>This specifies the path of the source <filepath>.mmp</filepath> file, relative

    71 to the current directory. </p>

    72 <p>If omitted, the source <filepath>.mmp</filepath> file is <codeph>project</codeph> <filepath>.mmp</filepath> in

    73 the current directory. </p>

    74 <p>Whether or not the <varname>source-path</varname> is specified, the generated

    75 makefile is always written into the current directory. </p>

    76 <p><b>project </b> </p>

    77 <p>This specifies the project for which to create the makefile. </p>

    78 <p><b>platform </b> </p>

    79 <p>This specifies the target platform, e.g. <codeph>thumb</codeph> or <codeph>winscw</codeph>. </p>

    80 <p><b>Command output </b> </p>

    81 <p>The output makefile name in most cases has the form <varname>project-name</varname>.<varname>platform-name</varname>.

    82 The exceptions are for <codeph>cw_ide</codeph>, which produces a <filepath>.xml</filepath> file,

    83 which can be imported into CodeWarrior, and <codeph>vc6</codeph> and <codeph>vc6winc</codeph>,

    84 which produce <filepath>.dsw</filepath> and <codeph>.dsp</codeph> files. </p>

    85 </conbody></concept>