Developer reports
Meson install destination report
Find shared lexical file destinations in a supplied Meson install plan.
Your inputs
Start with an exampleYour result
Example resultHow it works
Expand supplied {variables}, join relative destinations to the explicit prefix and normalize lexical dot segments. Group equal file destinations; retain unresolved paths and unexpanded directories.
Two example sources normalize to /usr/local/bin/app and form one shared destination group. The config.json destination is separate.
Limits
Up to 20000 entries, 10000 characters per expanded path and bounded expansion/output work. This compares planned path spellings, not file contents or real filesystem identity. Directory contents/exclusions remain unexpanded; overlaps are potential only. Missing/cyclic variables stay unresolved. ASCII folding is a chosen comparison, not a universal filesystem rule.