xcconfig

I use the following script to run XCode (7.0.1 7A1001) on OSX Yosemite 10.10.5: export FOO=bar #this should not be necessary, but just in case launchctl setenv FOO bar #should make it visible to all GUI applications (=XCode) open -a xcode I then open a workspace with two projects: App1 and App2 . In both projects I put $(HOME)/$(FOO) in the Header Search Paths field. In App1 it is resolved to /Users/ohads/bar as expected. In App2 it is resolved to /Users/ohads/ - note how the HOME variable is resolved, but the FOO variable is not. What's going on here? Why the discrepancy? How can I make FOO

I want to set Build Settings that are specific to each architecture (armv6 vs armv7). This is easy enough to do in the Xcode GUI, but I try to put all project configuration in .xcconfig files. Is it possible to replicate the following configuration (Thumb enabled for armv7, but not armv6 architectures) using .xcconfig files? Kurt Revis Yes, you can do that. SETTING_NAME[arch=arch_name] = some_value It's hard to find documentation on this. Apparently it was in the Xcode 3.0 release notes , but good luck finding those in Apple's current docs. To solve your particular problem: GCC_THUMB_SUPPORT

My project have multi-targets. Each target has its own Class file for setting stuff. I want to store that Class name in a target setting ( Info.plist or Target's Building setting). So that I can define which class I need to use in each target based on this setting. According to this question , I put "a target-specific User Defined variable" in each Target's Building Setting. But don't know how to get it back in my code? As the Info.plist file is preprocessed too, you can use this approach: Define a User defined setting in your build settings, for Example CLASS_NAME. And a key to your Info

I'm using Xcode 3.2 with xcconfig files. The files are organized by target. For example, I have a debug.xcconfig file and a release.xcconfig one. Both uses common settings, so I added a shared.xcconfig file which is included by both. The shared.xcconfig file looks like this: GCC_C_LANGUAGE_STANDARD = c99 GCC_WARN_ABOUT_RETURN_TYPE = YES GCC_WARN_UNUSED_VARIABLE = YES GCC_PREPROCESSOR_DEFINITIONS = SOME_COMMON_DEFINITIONS The debug.xcconfig file looks like this: #include "Shared.xcconfig" GCC_OPTIMIZATION_LEVEL = 0 Now, I would like to add a DEBUG preprocessor definition in the debug.xcconfig

so I used Venmo/Synx on my Xcode project with CocoaPods, and it completely screwed everything up. I was able to fix the Manifest.lock and Podfile.lock errors, but now I am getting this error: The file “Pods.debug.xcconfig” couldn’t be opened because there is no such file. (/Users/user/GitHub/xxxxxx/Pods/Pods/Target Support Files/Pods/Pods.debug.xcconfig) As you can see, the path is incorrect, as there is no Pods/Pods directory (there is one extra pod). How can I fix this? I have only added PODS_ROOT to the user-defined variable, as that fixed my Podfile and Manifest.lock files. Any help would

Is it possible to export xcode build settings to .xcconfig file? Other than just copy-paste it to text file line-by-line. Thanks! Michael M. Myers This SO answer helped me. Show the package contents of your project file (MyProject.xcodeproj) by two finger clicking on it in finder, then open the 'project.pbxproj' file in a text editor. Look for the section XCConfigurationList. It starts with /* Begin XCConfigurationList section */ . You will find all your targets and their respective builConfigurations. Now do a find (command - f) on the long hex ID to find the other occurance in the project

I'm using Xcode and .xcconfig files. I'm trying to append some values in the preprocessor definitions, but I simply can't make it work. I tried the following (as well as many variations of this), but no luck so far: GCC_PREPROCESSOR_DEFINITIONS = '$(GCC_PREPROCESSOR_DEFINITIONS) NEW_VALUE' The NEW_VALUE symbol is simply never added to the preprocessor definitions. Does anyone had success appending new values to variables in xcconfig files? For reasons stated in other answers to this question, you can't inherit values easily. I recommend defining your settings in cascade. Let's assume APP is