compile-analysis

To measure ACE Engine compile time and memory usage for a single file, run the analyze_compile.sh script with the target file and product name. It executes an enhanced build to capture real-world profiling metrics instead of estimates.

The best way to visualize header dependencies during ACE Engine builds is by parsing preprocessed .ii files with parse_ii.py. It generates a header-dependency tree to help diagnose complex include structures and reduce compilation overhead.

To diagnose a slow compiling file in an ACE Engine component, run the compile-analysis script on the specific file. It captures precise timing and memory metrics, allowing you to isolate bottlenecks and compare optimization results.

Yes, you can save a reusable script for repeatable ACE Engine compilation benchmarking by adding the --save-script flag. This generates a standalone compile script under out/{product} to validate changes without rerunning full builds.

Yes, preprocessed .ii files are required to analyze header dependencies in ACE Engine builds. The skill executes enhanced builds to generate these files, which parse_ii.py then parses to visualize the header-dependency tree.