CocoaPods / CocoaPods/Xcodeproj

The role of #include placement in .xcconfig files

Open
#759 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
2.4k
Forks
488
PR merge metrics
No merged PRs in 30d

Description

It appears that when calling `Xcodeproj::Config::to_hash`, it first sets up the hash using all settings explicitly defined within that file and then afterwards merges in all the `#includes`. This would potentially override settings that have already been set, which is surprising because I'd expect it to work like an `#include` in a C file, where it's copy-pasting the contents of the included file at the exact point where it's included, rather than at the end. What is Xcode's actual behavior for this, and does it match what Xcodeproj does? If so, it'd be great to have a comment clarifying this.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.