BuildSettingExtractor

BuildSettingExtractor copied to clipboard

Currently it looks like we write the destination folder and *then* figure out the project file is of an unsupported version. Would be better to either not write it in...

dempseyatgithub

Consider some way of handling build setting changes over time (extracting modern settings from older project)

1

This issue is related to issue #33, where a setting is now obsolete and is now represented by two settings. The old setting is still allowed by Xcode to be...

dempseyatgithub

In Xcode 11, the two Info.plist entries that change with each release are now automatically switched to two build settings. Since those two settings change with each release, it may...

dempseyatgithub

Consider hoisting common target settings to the project level

1

At the moment BSE performs all of its consolidation on the same 'level'. Common settings across multiple build settings at the project or target level are consolidated into a shared...

dempseyatgithub

Consider adding link to build setting documentation that Xcode now adds to its config file header comment

1

Would need to double check that the URL is valid over time - Apple docs have a habit of dead links.

dempseyatgithub

Ironically, would probably not take xcconfig files into account, at least not at first, but would try to see differences in two targets, trying at least to resolve project and...

dempseyatgithub

There may be cases where BSE needs to override any settings found in Xcode. A few current examples: - The SWIFT_VERSION setting has a name but an empty description. I...

dempseyatgithub

Consider either adding a command line tool or splitting out into a framework

2

Pull request #15 proposes factoring the extractor pieces into a separate framework. My comments there describe my initial thoughts about that. It may keep the complexity of the project reduced...

dempseyatgithub

Thank you

1

Not an issue, but wanted to say **thank you** for this project.

palaniraja

support cli

1

CharlieSuP1