build-error-analyzer

To analyze OpenHarmony build failures, the Skill extracts the latest error block from your build logs into last_error.log and classifies the root cause using known error signatures and historical cases. It identifies whether the issue stems from linker errors, compilation errors, or GN/Ninja build-system failures.

Undefined symbol linker errors during ace_engine builds are typically caused by missing .cpp files in BUILD.gn ace_core_ng_source_set, ACE_FORCE_EXPORT and libace.map export gaps, or template visibility issues. The Skill matches these historical patterns to recommend targeted file-path fixes.

To fix GN build configuration errors, the Skill maps the extracted error patterns from out/<product>/last_error.log to concrete remediation steps. It provides targeted file-path guidance for OpenHarmony build configuration adjustments without automatically modifying your files.

Yes, the log analysis workflow supports SDK builds by extracting errors specifically from out/sdk/last_error.log. It ensures analysis is based only on the latest error block, avoiding stale errors from older logs in both normal product builds and special SDK builds.

OpenHarmony builds may continue failing if older stale errors are analyzed instead of the latest error block. The Skill enforces strict log-source discipline by exclusively extracting the most recent error block into last_error.log to ensure accurate pattern-to-case matching and fix recommendations.

You need to update ACE_FORCE_EXPORT and libace.map when the Skill detects linker errors related to symbol export gaps. It recognizes these specific historical cases and recommends the exact build-system changes needed to resolve the undefined symbol issues in your OpenHarmony build.