--- a/Symbian3/PDK/Source/GUID-7F091034-43FE-40B1-AAE2-C8AD010F4C1C.dita Thu Mar 11 15:24:26 2010 +0000
+++ b/Symbian3/PDK/Source/GUID-7F091034-43FE-40B1-AAE2-C8AD010F4C1C.dita Thu Mar 11 18:02:22 2010 +0000
@@ -1,46 +1,46 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
-<!-- This component and the accompanying materials are made available under the terms of the License
-"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:
--->
-<!DOCTYPE reference
- PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="GUID-7F091034-43FE-40B1-AAE2-C8AD010F4C1C" xml:lang="en"><title>SysLibs
-Test Suite Details</title><prolog><metadata><keywords/></metadata></prolog><refbody>
-<section> <title>Test Script Source Tree Location</title> <p>Descriptions
-of the test cases in this test suite can be found at the following location: </p> <p> <filepath>...\syslibsapitest\syslibssvs\ecom\scripts\SYSLIB-ECOM-PublicAPI.script</filepath> </p> </section>
-<section><title>Test Script EPOC tree Location</title> <p>When the tests are
-built for emulator or hardware (winscw or armv5), the script is exported into
-the following location in the epoc tree. </p> <p> <filepath>%EPOCROOT%\epoc32\data\Z\ecom\SYSLIB-ECOM-PublicAPI.script</filepath> </p> </section>
-<section><title>Test Script Build Location</title> <p>When the tests are built,
-the scripts are built into the following location </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\ecom</filepath> </p> <p> <b>Note:</b> When the tests are built to be executed on hardware the
-files are built into the z: drive of the ROM. </p> </section>
-<section><title>Test Data Source Tree Location</title> <p>The test suite contains
-following test data files: </p> <p> <filepath>...\syslibsapitest\syslibssvs\ecom\testdata\SYSLIB-ECOM-PublicAPI.ini</filepath> </p> <p>The
-global environment file located at: </p> <p> <filepath>...\syslibsapitest\syslibssvs\testdata\<platform>\t_syslibs.ini</filepath> </p> </section>
-<section><title>Test Data Files EPOC Tree Location</title> <p>When the tests
-are built for emulator or hardware (winscw/armv5), the data files are exported
-into the following location in the epoc tree. </p> <ul>
-<li id="GUID-59493D8D-9350-5EBA-A7CC-D4276340CBC3"><p> <filepath>%EPOCROOT%\epoc32\data\Z\ecom\SYSLIB-ECOM-PublicAPI.ini</filepath> </p> </li>
-<li id="GUID-62EAD10E-A155-50F3-965C-C36242479C9C"><p> <filepath>%EPOCROOT%\epoc32\data\Z\syslibs\t_syslibs.ini</filepath> </p> </li>
-</ul> </section>
-<section><title>Test Data Files Emulator Location</title> <p>When the tests
-are built, the test data files are built into the following location </p> <p> <filepath>%EPOCROOT%\epoc32\
- release\winscw\<udeb/urel>\Z\ecom\.</filepath> </p> <p> <b>Note:</b> When
-the tests are built to be executed on hardware the files are built into the
-z: drive of the ROM </p> </section>
-<section><title>Test .driver File</title> <p>The <filepath>syslibs.driver</filepath> file
-found in </p> <p> <filepath>…\syslibsapitest\syslibssvs\testsuites\syslibs\</filepath> </p> <p>is
-used by the test driver to construct the test suite tree structure and export
-all the appropriate files to the correct location in the epoc32 tree and on
-the device. </p> <p>When the tests are built, the <filepath>.driver</filepath> file
-can be found in the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\testdriver\testproduct</filepath> </p> </section>
-<section><title>TCS file source location</title> <p>The <filepath>.tcs</filepath> file
-can be found at the following location: </p> <p> <filepath>...\syslibsapitest\syslibssvs\config\t_syslibs.tcs</filepath> </p> </section>
-<section><title>TCS file build location</title><p>When the tests are built,
-the <filepath>.tcs</filepath> file is generated into the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\ecom</filepath> </p> </section>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License
+"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:
+-->
+<!DOCTYPE reference
+ PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<reference id="GUID-7F091034-43FE-40B1-AAE2-C8AD010F4C1C" xml:lang="en"><title>SysLibs
+Test Suite Details</title><prolog><metadata><keywords/></metadata></prolog><refbody>
+<section> <title>Test Script Source Tree Location</title> <p>Descriptions
+of the test cases in this test suite can be found at the following location: </p> <p> <filepath>...\syslibsapitest\syslibssvs\ecom\scripts\SYSLIB-ECOM-PublicAPI.script</filepath> </p> </section>
+<section><title>Test Script EPOC tree Location</title> <p>When the tests are
+built for emulator or hardware (winscw or armv5), the script is exported into
+the following location in the epoc tree. </p> <p> <filepath>%EPOCROOT%\epoc32\data\Z\ecom\SYSLIB-ECOM-PublicAPI.script</filepath> </p> </section>
+<section><title>Test Script Build Location</title> <p>When the tests are built,
+the scripts are built into the following location </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\ecom</filepath> </p> <p> <b>Note:</b> When the tests are built to be executed on hardware the
+files are built into the z: drive of the ROM. </p> </section>
+<section><title>Test Data Source Tree Location</title> <p>The test suite contains
+following test data files: </p> <p> <filepath>...\syslibsapitest\syslibssvs\ecom\testdata\SYSLIB-ECOM-PublicAPI.ini</filepath> </p> <p>The
+global environment file located at: </p> <p> <filepath>...\syslibsapitest\syslibssvs\testdata\<platform>\t_syslibs.ini</filepath> </p> </section>
+<section><title>Test Data Files EPOC Tree Location</title> <p>When the tests
+are built for emulator or hardware (winscw/armv5), the data files are exported
+into the following location in the epoc tree. </p> <ul>
+<li id="GUID-59493D8D-9350-5EBA-A7CC-D4276340CBC3"><p> <filepath>%EPOCROOT%\epoc32\data\Z\ecom\SYSLIB-ECOM-PublicAPI.ini</filepath> </p> </li>
+<li id="GUID-62EAD10E-A155-50F3-965C-C36242479C9C"><p> <filepath>%EPOCROOT%\epoc32\data\Z\syslibs\t_syslibs.ini</filepath> </p> </li>
+</ul> </section>
+<section><title>Test Data Files Emulator Location</title> <p>When the tests
+are built, the test data files are built into the following location </p> <p> <filepath>%EPOCROOT%\epoc32\
+ release\winscw\<udeb/urel>\Z\ecom\.</filepath> </p> <p> <b>Note:</b> When
+the tests are built to be executed on hardware the files are built into the
+z: drive of the ROM </p> </section>
+<section><title>Test .driver File</title> <p>The <filepath>syslibs.driver</filepath> file
+found in </p> <p> <filepath>…\syslibsapitest\syslibssvs\testsuites\syslibs\</filepath> </p> <p>is
+used by the test driver to construct the test suite tree structure and export
+all the appropriate files to the correct location in the epoc32 tree and on
+the device. </p> <p>When the tests are built, the <filepath>.driver</filepath> file
+can be found in the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\testdriver\testproduct</filepath> </p> </section>
+<section><title>TCS file source location</title> <p>The <filepath>.tcs</filepath> file
+can be found at the following location: </p> <p> <filepath>...\syslibsapitest\syslibssvs\config\t_syslibs.tcs</filepath> </p> </section>
+<section><title>TCS file build location</title><p>When the tests are built,
+the <filepath>.tcs</filepath> file is generated into the following location: </p> <p> <filepath>%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\ecom</filepath> </p> </section>
</refbody></reference>
\ No newline at end of file