Core Technical Philosophy of Kunpeng Native Development
Kunpeng native development allows developers to leverage Kunpeng hardware, openEuler, Kunpeng DevKit, and Kunpeng BoostKit for streamlined cross-platform development using a single codebase and pipeline. This approach enhances development efficiency and application performance.
Kunpeng native development consists of the coding phase and pipeline phase.
- Coding phase: Use the Kunpeng DevKit and BoostKit to write code more efficiently on the Kunpeng architecture.
- Pipeline phase: The Kunpeng DevKit CLI can be connected to the Continuous Integration (CI)/Continuous Delivery (CD) pipeline within one hour, making it easy to deliver versions for multiple architectures.
Figure 1 Core technical philosophy
- Quick integration and release: The Kunpeng DevKit plugin can be connected to the CI/CD pipeline (Jenkins or GitLab) within one hour, accelerating Kunpeng pipeline setup and version release.
- Kunpeng affinity and ultimate performance: The Kunpeng pipeline uses Kunpeng analysis tools, compilers, and performance tuning tools to improve application performance.
- Architecture compatibility: One set of pipeline allows building and testing different versions for multiple processor architectures.
- Unified codebase: One set of code is suitable for multiple processor platforms.