dbgagents/trkagent/toolsstarter/toolsstarterclient/group/toolsstarterclient.mmp
author ravikurupati
Tue, 02 Mar 2010 10:33:16 +0530
changeset 0 c6b0df440bee
permissions -rw-r--r--
Initial contribution of EPL licensed sources

/*
* Copyright (c) 2006 Nokia Corporation and/or its subsidiary(-ies).
* All rights reserved.
* This component and the accompanying materials are made available
* under the terms of "Eclipse Public License v1.0"
* which accompanies this distribution, and is available
* at the URL "http://www.eclipse.org/legal/epl-v10.html".
*
* Initial Contributors:
* Nokia Corporation - initial contribution.
*
* Contributors:
*
* Description: 
*
*/

#include <platform_paths.hrh>

TARGET		  toolsstarterclient.dll
TARGETTYPE	  dll
UID 0x1000008d 0x200170B4

capability All -Tcb

USERINCLUDE	 ../inc
USERINCLUDE   ../../common
USERINCLUDE ../../toolsstarterserver/inc
//SYSTEMINCLUDE   \epoc32\include
MW_LAYER_SYSTEMINCLUDE

SOURCEPATH	  ../src

SOURCE		  toolsclientdefs.cpp toolsclientdllmain.cpp toolsclientutils.cpp toolsclientsession.cpp

// In order to use .def files to freeze code you must use one or more DEFFILE lines;
// see the ones commented out below for examples.
// By default, the build tools look for the WINSCW def file in a BWINS directory
// (at the same level as the directory containing the mmp file), 
// the GCC ARM def file in a BMARM directory, and the ARMV5 def file in a EABI directory. 
// If your .def files are stored in these default locations, you can simply specify the
// .def filename(s) with no path. If you want to store .def files in non-default 
// locations, you will need to specify the paths in the DEFFILE statement(s).

//The following commented out code shows how the build system uses the implicit
// location for defiles. To create the DEF files Choose Project > Freeze Exports from Carbide
// or run 'abld freeze' from the command-line
//#ifdef MARM
DEFFILE ../eabi/toolsstarterclient.def
//#endif

nostrictdef

LIBRARY		 euser.lib