The following table lists the messages that may be displayed when analysing files and filtering reports.
Message | Explanation | Action |
---|---|---|
No filetypes are specified. Specify type of files to
be analysed. |
Both analysis type check boxes are unchecked in the analysis type selection page. |
Select at least one type of analysis (headers and/or libraries). |
Version string cannot be null |
The Symbian SDK version list box is empty. |
Select or type in the version number of the selected SDK in the product SDK version list box. |
Root directory can not be null |
On the headers page, the directory path is empty under the header selection group. |
Type in or browse for the directory path of header files. |
No header files are selected. Select files to be analysed.
|
In the headers analysis page, the header file list is empty. |
Add headers using the Add files button. |
Select header types to be analysed. |
On the header analysis page, nothing is selected under the Selection of file types to be analysed group. |
Select file types from the four options (.h , .hrh , .mbg , .rsg). |
Selected types do not match with the selected header
files. |
Files added to the headers list in the header analysis page do not match with the file types selected. For example, .mbg or.rsg files cannot be selected for header analysis. |
Remove all the files from the list or add only the files of the selected type. In addition, you can also check types of files in the list. |
No platform header paths are defined. This may cause
compilation errors. |
On the platform headers page, the list of system include paths is empty. |
Add system include paths using the Add includes button. |
No library files are selected for analysis. |
On the library analysis page, the library list is empty. |
Add library files using the Add files button. |
No Baseline Profiles are Selected. |
No baseline profiles are created and the list box on the baseline selection page is empty. |
Click the Configure Baseline profile button to start creating a profile. |
Report FileName can not be null. |
The filename is empty on the Report file configuration page. |
Type any name into the text field. |
Report File Path can not be null. |
The output path directory of the reports is empty. |
Provide the directory path using the Browse button. |
Add minimum one report file. |
In the Report Filter Wizard, the list of report files is empty. |
Add report files to be filtered. |
Checkbc.py file missing in given directory. |
The selected core tools version does not contain checkbc.py file. |
Select a valid core tools package from the Preferences page. |
Coretools are not compatible. |
The data version of the selected core tools does not match the Compatibility Analyser tool. |
Select a valid core tools package from the Preferences page. |
Select profile from the list |
No profile is selected in the profile combo box. |
Select a profile from the list if profiles already exist. Or, click the Configure Baseline profile button to start creating a profile. |
Given coretools are not compatible. Currently supported
DATAVERSION is -. Would you like run the analysis with the default core tools?
|
The selected core tools are not compatible with tool. |
Click Yes to run the analysis with the default tools provided by the tool. |
Please update the com.nokia.s60tools.compatibilityanalyser.corecomponents
plugin. The one being used is incompatible with the tool. |
The core tool version provided by the tool is invalid. |
Update the core components plugin from Software updates > Find and install… |
I/O error while opening the connection.
Please check the - Internet connection & Provided URL |
If you are not connected to the intranet while downloading core tools or baseline profiles. |
Connect to the intranet. |
DSO paths list cannot be empty. |
The DSO path list is empty on the library analysis page. |
Add a minimum of one directory of .lib/.dso files. |
DLL paths list cannot be empty. |
The DLL path list is empty on the library analysis page. |
Add a minimum of one directory of .dll files. |