|
1 ======================================================================== |
|
2 RELEASE NOTE FOR APPDEP, 2.2 |
|
3 ======================================================================== |
|
4 |
|
5 Product Description: |
|
6 ==================== |
|
7 AppDep is a command line tool that can be used to resolve static |
|
8 dependency information of a component within a Symbian OS build (either |
|
9 platform or custom). The tool generates a cache file by reading the data |
|
10 from all binaries and import libraries within a release, by using an |
|
11 external compiler tool set. The use of a cache file is a fast way to make |
|
12 a dependency review, such as what dependencies a binary has, and functions |
|
13 and ordinals used in a binary, and to generate dependency lists to a |
|
14 component or a function. The tool can also be used to view the properties |
|
15 of a binary. |
|
16 |
|
17 Features: |
|
18 ========= |
|
19 - Generates a cache file appdep-cache-symbol-tables.txt which contain |
|
20 symbol tables of all import libraries within a release |
|
21 - Generates a cache file appdep-cache-dependencies.txt which contain |
|
22 dependency information of all binaries within a release |
|
23 - Reading data from AppDep generated cache files or from platform |
|
24 generated StaticDependencies.txt |
|
25 - Include SIS files under analysis |
|
26 - Support for defining multiple target types |
|
27 - Support for reading binaries from a release or a debug build |
|
28 - Support for reading .lib files or .dso files |
|
29 - Display properties of a file |
|
30 - Print all static dependencies of a component |
|
31 - Print all components that depends on a component |
|
32 - Print all functions used by a component |
|
33 - Print all components that are using a function |
|
34 |
|
35 Fixed issues: |
|
36 ============= |
|
37 - Added support for components that include "-" character in the middle of the component name i.e. now |
|
38 also imported function lines of format '27 imports from libdbus-utils{000a0000}[20010154].dll' are parsed |
|
39 correctly from dump created by elftran.exe. |
|
40 - Fixed issue 'command '-showfunctions' may report functions with same ordinal twice' which was due to duplicate |
|
41 import function instances found from cache file. Now the possible duplicate import function instances are detected |
|
42 during cache creation and only one import function instance is stored. |
|
43 |
|
44 Enhancements: |
|
45 ============= |
|
46 - Appdep now scans *.agt and *.fxt files as binaries |
|
47 - Changed tool to use elftran.exe instead petran.exe for GCCE and RVCT toolchains (petran.exe is still used for GCC). |
|
48 |
|
49 New Features: |
|
50 ============= |
|
51 |
|
52 System Requirements: |
|
53 ==================== |
|
54 Basic Requirements: |
|
55 - Windows 2000 |
|
56 - External RVCT or GCCE tool chain installed when Symbian OS 9.x is |
|
57 being used |
|
58 - Symbian OS development environment installed including all related |
|
59 import libraries (.lib or .dso) |
|
60 |
|
61 Compatibility Issues: |
|
62 ===================== |
|
63 N/A |
|
64 |
|
65 Known Issues: |
|
66 ============= |
|
67 |
|
68 RVCT toolset slowness |
|
69 --------------------- |
|
70 - If your installed RVCT toolset does not have a fixed license, it will |
|
71 get a license for each import library every time. This may cause the |
|
72 cache generation become very slow. If this is causing problems, try |
|
73 --uselibs parameter or use GCCE tool chain instead. |
|
74 |
|
75 C++filt location when RVCT toolchain is used |
|
76 -------------------------------------------- |
|
77 - When you RVCT toolchain, you must also specify a location to C++filt |
|
78 tool since RVCT toolchain does not provide that. It is recommended to |
|
79 use the cfilt.exe provided with AppDep installed since it has been |
|
80 tested to work correctly. C++filt.exe provided by the platform cannot |
|
81 be used since it is not compatible. |
|
82 |
|
83 Copyright (c) 2001-2009 Nokia Corporation and/or its subsidiary(-ies). |
|
84 All rights reserved. |
|
85 |
|
86 This component and the accompanying materials are made available |
|
87 under the terms of "Eclipse Public License v1.0" |
|
88 which accompanies this distribution, and is available |
|
89 at the URL "http://www.eclipse.org/legal/epl-v10.html". |
|
90 |