build-system-expert

To fix Android.bp dependency errors, verify module definitions, visibility, and enabled flags across build directories. Check for disabled module dependencies and duplicate module errors, referencing canonical build/make/core/main.mk logic to adjust boundaries.

Duplicate module errors in Soong and Kati occur when multiple Android.bp or Android.mk files define the same module name. Resolve this by locating the conflicting definitions and adjusting the module visibility or enabled flags.

VNDK boundaries dictate module placement and linking between system, vendor, product, and odm partitions. Correctly configuring VNDK rules ensures modules are placed on the appropriate partition image without violating build system restrictions.

Diagnose ninja build failures from Kati rule issues by inspecting Android.mk edits and tracing dependency chains. Ensure your troubleshooting respects Android 15 build system restrictions and prebuilts workflow conventions.

Yes, the build system guidance covers toolchain and bionic workflows. It grounds troubleshooting in Soong and Kati conventions specifically for Android 15 build, prebuilts, toolchain, and bionic directories to prevent hallucinated paths.

Check visibility flags when encountering module linking failures or depends on disabled module errors. Adjusting visibility in Android.bp files allows permitted modules to access dependencies across different build directories.