How eellak/build-recorder works
Main System Components
a) Command Line Interface Layer
• Entry point (main.c)
• Command processing and initialization
• Output file handling
b) Core Tracing System
• Process tracer component (tracer.c)
• Record management (record.c, record.h)
• Hash computation system (hash.c, hash.h)
c) Data Management Layer
• Type definitions (types.h)
• RDF Turtle output generation
• File system interactions
Specific Implementation Details
Use these visual elements:
a) Components:
• Rectangle: Main process components
• Hexagon: System call interception points
• Diamond: Decision points in the tracing logic
• Blue: Core tracing components
• Green: File system interactions
• Yellow: Data processing components
• Gray: External system elements (build process being traced)
Key Relationships to Highlight
• Bidirectional relationship between tracer and target process
• File system monitoring paths
• Demonstrate data flow from system call interception to RDF generation
Top Layer: User Interface/Input
↓
Middle Layer: Process Tracing & Monitoring
↓
Bottom Layer: Data Processing & Output Generation
Additional Notes
• A note about the LGPL-2.1-or-later license
• Version compatibility information (Linux 5.3+)
• Integration points with build systems
This architecture reflects a tool that operates at the system level while maintaining a clean, modular design that separates core functionality (tracing, recording, hashing) from input/output handling.