Unity의 Android 애플리케이션 빌드 방법

Unity uses Gradle to build Android applications so it’s useful to understand the build process and how Unity interacts with Gradle. Gradle lets you use Player Settings and other Unity windows to configure most aspects of the final build, however for more control, you must overwrite manifest and template files, or export your project and edit it in Android Studio.

빌드 프로세스

Android 애플리케이션을 빌드하려면 다음 단계를 따르십시오.

1. Unity calls OnModifyAndroidProjectFiles for all AndroidProjectFilesModifier interfaces. You can use this callback to set up prerequisites for modifying Android Gradle project files. For more information, refer to AndroidProjectFilesModifier.Setup.
2. Unity collects project resources, code libraries, plug-ins, Gradle templates, and manifest templates from your Unity project and uses them to create a valid Gradle project.
3. Unity adds and updates values inside Gradle templates and manifest files based on the Unity project’s Player Settings and Build Settings.
4. If you chose to export the project and not build it, and use the IL2CPP scripting backend, Unity places C++ source files produced from your C# scripts into the Gradle project. Otherwise, if you chose to build the project, Unity places the libil2cpp.so library into the Gradle project.
5. Unity calls OnModifyAndroidProjectFiles for all AndroidProjectFilesModifier interfaces. You can use this callback to modify Gradle project file values. For more information, refer to Modify Gradle project files with the Android Project Configuration Manager.
6. Unity calls OnPostGenerateGradleAndroidProject for all IPostGenerateGradleAndroidProject interfaces. You can use this callback to modify or move files before Gradle builds the application. Note: OnPostGenerateGradleAndroidProject is deprecated, use OnModifyAndroidProjectFiles instead.
7. Unity runs Gradle to build the application from the Gradle project. Gradle merges the Unity Library Manifest, Unity Launcher Manifest, and plug-in manifests into one Android App Manifest file.

증분 빌드 파이프라인

Unity는 Android용 플레이어를 빌드할 때 증분 빌드 파이프라인을 사용합니다. 다음 Android 관련 증분 빌드 파이프라인 동작을 참조하십시오.

• Unity 증분 빌드/생성:
  • Gradle 파일
  • 매니페스트 파일
  • 에셋 팩
  • APK 확장 파일(obbs)
  • 압축되지 않은 에셋 분할
  • Android 심볼 zip 파일
• Unity 증분 복사:
  • 플레이어 바이너리
  • Gradle 리소스 빌드 프로세스의 마지막 단계는 Gradle을 실행하는 것입니다. 이 시점부터 빌드 프로세스는 증분 빌드 파이프라인을 사용하지 않으며 종속성을 추적하는 것은 Gradle에 달려 있습니다.

If you implement IPostGenerateGradleAndroidProject and modify or move any Android file or asset that the incremental build pipeline uses, it can cause issues when you build your project. If you only want to modify Gradle project files, it’s best practice to use the Android Project Configuration Manager instead of IPostGenerateGradleAndroidProject. If you must use IPostGenerateGradleAndroidProject for your use case and need to work around incremental build pipeline issues, refer to Creating non-incremental builds.