Symbian3/SDK/Source/GUID-B6B54E07-3B34-5D5C-8815-93383FA8FB4B.dita
changeset 13 48780e181b38
parent 12 80ef3a206772
child 14 578be2adaf3e
equal deleted inserted replaced
12:80ef3a206772 13:48780e181b38
     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-B6B54E07-3B34-5D5C-8815-93383FA8FB4B" xml:lang="en"><title>How
       
    13 to use abld</title><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    14 <p>The <filepath>abld.bat</filepath> batch file is used to control all aspects
       
    15 of building a project. It is created in the current directory by the <filepath>bldmake</filepath> tool
       
    16 from a component description file <filepath>bld.inf</filepath>. </p>
       
    17 <p>The syntax reference for this tool exhaustively lists all of the possible
       
    18 build operations which can be performed using <filepath>abld</filepath>. The
       
    19 tool's flexibility obscures the fact that most Symbian developers will only
       
    20 need to use two commands: one for cleaning up all files created in a previous
       
    21 build, and another for building the current project. </p>
       
    22 <section><title>Cleaning</title> <p>Cleaning removes all the intermediate
       
    23 files created during compilation, and all the executables and import libraries
       
    24 created by the linker. The simplest invocation of this operation deletes the
       
    25 files for all platforms, and projects belonging to the component. </p> <p><userinput>abld
       
    26 clean</userinput> </p> <p>It is also possible to specify the platform and
       
    27 build variant to be cleaned. </p> </section>
       
    28 <section><title>Building</title> <p> <filepath>abld</filepath> builds projects
       
    29 based on the makefiles created by <filepath>bldmake</filepath> from the component
       
    30 information file and project files. </p> <p>The simplest invocation of this
       
    31 command builds the project for all possible build variants: </p> <p><userinput>abld
       
    32 build</userinput> </p> <p>However building for a platform can take some time,
       
    33 and it is usual to only specify the platform required. For example, to build
       
    34 the debug version on the WINSCW platform specify: </p> <p><userinput>abld
       
    35 build winscw udeb</userinput> </p> <p>or to build the release version for
       
    36 ARMV5 use: </p> <p><userinput>abld build armv5 urel</userinput> </p><note>The <codeph>build</codeph> command
       
    37 combines the other <filepath>abld</filepath> commands: <codeph>export</codeph>, <codeph>makefile</codeph>, <codeph>library</codeph>, <codeph>resource</codeph>, <codeph>target</codeph> and <codeph>final</codeph>, which are carried out
       
    38 in turn. </note> <p><b>See also </b> </p> <p><xref href="GUID-5A3A3EA0-6C03-56F2-B277-B61A27ABFF9E.dita">Abld
       
    39 syntax</xref> </p><p><xref href="GUID-793A5EF9-CC16-5EEB-9011-6431EA76EB15.dita">Using
       
    40 bldmake</xref> </p> </section>
       
    41 </conbody></concept>