How marcrespass/buildsettingextractor works
Project type and purpose
• This is a macOS desktop utility (AppKit) written in Objective-C whose sole purpose is to extract Xcode build settings from a dropped .xcodeproj file and emit .xcconfig files. It includes a GUI (main window + preferences), core processing components, and a test bundle.
Top-level components
• BuildSettingExtractor.xcodeproj (Xcode project file)
• BuildSettingExtractor/ (AppKit source & assets)
• Preferences/ (Preferences window UI & controllers)
• Config/ (xcconfig files used to build this utility)
• BuildSettingExtractorTests/ (unit tests & test fixtures)
Main architectural layers & components
a. User Interface Layer (blue)
• MainWindow.xib + DragFileView
• AppDelegate (wires up drag/drop)
• Preferences.storyboard + PreferencesViewController + sub-controllers
b. Core Extraction Layer (green)
• BuildSettingExtractor (entry point for extraction logic)
• BuildSettingInfoSource (reads project.pbxproj + BuildSettingInfoSubpaths.plist)
• BuildSettingCommentGenerator (formats comments for each setting)
• SampleFileStructureGenerator (used in Preferences preview)
c. Persistence / File I/O Layer (orange)
• Destination folder I/O: writing shared & per-target .xcconfig files
• UserDefaults (stores preferences from PreferencesViewController)
d. Test Layer (gray)
• BuildSettingExtractorTests.m (exercise extraction on sample .xcodeproj.test files)
• TestFiles folder with malformed/good project fixtures
Relationships & data flow
1. User drags a .xcodeproj onto the Main Window (DragFileView)
2. AppDelegate intercepts the drop, invokes BuildSettingExtractor
3. BuildSettingExtractor reads project file via BuildSettingInfoSource
4. For each target / configuration:
– BuildSettingInfoSource yields raw build settings
– BuildSettingCommentGenerator prepends descriptive comments
– File I/O layer writes out shared & per-configuration .xcconfig files
5. Preferences subsystem supplies user-configured options (via UserDefaults) to the Extraction Layer (e.g., toggle comments on/off, grouping behavior)
6. Tests import the BuildSettingExtractor module, feed it test projects, and assert expected generated output
Architectural patterns & principles
• MVC-ish separation in the UI: XIBs/Storyboards + Controllers + AppDelegate as coordinator
• Single Responsibility:
• BuildSettingExtractor orchestrates workflow
• InfoSource handles project parsing
• CommentGenerator handles formatting
• Dependency injection: Preferences state injected into core components
• Testability: core logic is decoupled from UI for unit testing