Rate This Document
Findability
Accuracy
Completeness
Readability

Performing Porting Analysis

Scan the Flink installation package by following instructions in Kunpeng Porting Advisor Case Study to know the third-party dependency packages to be ported. See Table 1.

Table 1 Software porting analysis result

Original JAR Package

SO File

scala-compiler-2.11.12.jar

libjansi.so

flink-shaded-netty-4.1.32.Final-7.0.jar

liborg_apache_flink_shaded_netty4_netty_transport_native_epoll_x86_64.so

frocksdbjni-5.17.2-artisans-1.0.jar

librocksdbjni32.so,librocksdbjni64.so,librocksdbjnile.so

flink-shaded-netty-tcnative-dynamic-2.0.25.Final-7.0. jar

liborg_apache_flink_shaded_netty4_netty_tcnative_linux_x86_64.so,liborg_apache_flink_shaded_netty4_netty_tcnative_linux_x86_64_fedora.so

The purpose is to identify the JAR files to be recompiled so that they can be ported to the Kunpeng platform.