{"id":1489,"date":"2021-02-18T09:27:43","date_gmt":"2021-02-18T02:27:43","guid":{"rendered":"https:\/\/beadgrup.com\/news\/?p=1489"},"modified":"2021-10-21T08:18:55","modified_gmt":"2021-10-21T01:18:55","slug":"konsep-pengembangan-android","status":"publish","type":"post","link":"https:\/\/beadgrup.com\/news\/konsep-pengembangan-android\/","title":{"rendered":"Android Development Concept"},"content":{"rendered":"\n

Introduction<\/p>\n\n\n\n

This section provides a high-level explanation of how the NDK works. The Android NDK is a set of tools that allow you to embed C or C++ code (\u201cnative code\u201d) into your Android applications. The ability to use native code in Android apps can be especially useful for developers looking to do one or more of the following:<\/p>\n\n\n\n

  1. Adapting applications across platforms<\/li>
  2. Reuse existing libraries or provide their own libraries for reuse.<\/li>
  3. Improves performance in certain cases, especially in compute-heavy applications such as games.<\/li><\/ol>\n\n\n\n

    Main component:<\/p>\n\n\n\n

    1. Native shared libraries: The NDK builds these libraries, or .so files, from C\/C++ source code.<\/li>
    2. Native static libraries: The NDK can also build static libraries, or .a files, which can be linked to other libraries.<\/li>
    3. Java Native Interface (JNI): JNI is an interface for Java and C++ components to communicate with each other. This guide assumes that you are familiar with JNI.<\/li>
    4. Application Binary Interface (ABI): The ABI defines exactly how the application’s machine code interacts with the system at the expected runtime. The NDK creates a .so file based on this definition. Different ABIs correspond to different architectures: The NDK includes ABI support for 32-bit ARM, AArch64, x86, and x86-64.<\/li>
    5. Manifest: If you’re writing an app without a Java component, you must declare a class NativeActivity in your manifest<\/li><\/ol>\n\n\n\n

      Plot<\/p>\n\n\n\n

      1. Design your application, determine which parts will be implemented in Java, and which parts will be implemented as native code.<\/li>
      2. Create an android application project like you do for any other application project<\/li>
      3. If you are writing a native-only app declare the NativeActivity class in Android Manifest.xml<\/li>
      4. Create an Android.mk file that describes the native library, including the name, flags, linked libraries and the source to be compiled in the \u201cJNI\u201d directory<\/li>
      5. If you wish, you can create an Application.mk file that configures the target ABI, toolchain, moderilis\/debug and STL.<\/li>
      6. Place your native sources in the project’s jni directory<\/li>
      7. Use ndk-build to compile the native(.so, .a) libraries.<\/li>
      8. Create a Java component, which will generate a .dex executable file.<\/li>
      9. Package everything into an APK file containing the .so, .dex, and other files needed to run the app.<\/li><\/ol>\n\n\n\n

        The need for digital IT is needed in daily activities, Bead IT Consultant is the right choice as your partner, visit our website by clicking this link:\u00a0www.beadgroup.com<\/a><\/p>\n\r\n