Viewing Analysis Results

Prerequisites

The analysis task is complete.

The porting reports vary with the target OS because different OSs support different SO libraries.

Procedure

1. Click Software Porting Assessment from the navigation pane on the left. Historical reports are listed.
2. In the historical report list, click the report name of the analysis task. The report page is displayed.
   Figure 1 Porting assessment report
   

   Table 1 Parameters in the porting assessment report

   Parameter	Description
   Total Files	Total number of architecture-related files on which the software package depends.
   Compatible	Already compatible with the target hardware platform.
   Adaptable for Compatibility	Download the file package from the Kunpeng image repository and use it to replace the current files. For details, see the handling suggestions in Architecture-Related Dependencies.
   Unconfirmed	Perform required operations to ensure compatibility with the target hardware platform. For details, see the handling suggestions in Architecture-Related Dependencies.
   Architecture-Related Dependencies	Displays the SO files. You can click Download in the Handling Suggestions column to download the dynamic libraries, static library files, software packages, executable files, and JAR packages that are compatible with the Kunpeng platform. You can also download the source code of the Kunpeng version and compile it. For some non–open-source dependency files, the download URLs are not available. You need to obtain the files yourself and use them to replace the architecture-related dependency files. For a file whose compatibility with the Kunpeng platform is unknown, verify its compatibility on the Kunpeng platform first. If it is not compatible with the Kunpeng platform, obtain a compatible version from the vendor, obtain the source code and compile it, or use alternative software. NOTE: If Handling Suggestions indicates that the file is compatible with the Kunpeng platform (the file and link exist in the trustlist used by the tool and the Download button is displayed), the analysis object is a migrated software package or source package, and the x86 dependency file has a corresponding Kunpeng dependency file on the Kunpeng platform. Therefore, you do not need to replace the file.

Follow-up Procedure

Different software packages may be processed in different ways.

1. Prepare dependencies.

   Take dependencies that are adaptable for compatibility in Figure 2 as an example. Click Download to obtain the dependency files.

   Figure 2 Dependencies
   
2. You can use the 7-Zip tool to open the RPM package and replace the JAR package in the preceding path with the RPM package.