Replacing Dependency Files

During software porting assessment, if some dependency files (such as SO dynamic libraries and JAR packages) are incompatible with the target architecture, handle them as follows.

Procedure

Obtain the software packages.
Obtain the corresponding software package (RPM/DEB/JAR) or source code based on the Handling Suggestions under Architecture-Related Dependencies.
- Click Download to obtain the software packages (RPM/DEB/JAR).
- Go to the community to download the source code.
Obtain the dependency files.
- RPM package
  - Method 1: Directly install the package to generate the dependency files.
```
rpm -ivh package.rpm
```
  - (Recommended) Method 2: Extract the RPM package and find the dependency files.
```
rpm2cpio package.rpm | cpio -idmv
```
  package indicates the name of the software package to be downloaded.
- DEB package
  - Method 1: Directly install the package to generate the dependency files.
```
dpkg -i package.deb
```
  - (Recommended) Method 2: Extract the DEB package and find the dependency files.
```
dpkg-deb -x package.deb ./extract_dir
```
  - package indicates the name of the software package to be downloaded.
  - extract_dir indicates the extracted directory.
- JAR package: Use the downloaded JAR package to replace the incompatible JAR package in the porting environment.
- Source code: Go to the community to obtain the source code and install it based on the integrated guide to generate dependency files.
Replace the dependency files in the Dependency File Path directory with the newly generated or extracted dependency files.

Parent topic: References