andymatuschak/TestMigration — Issue #53: Including Sparkle via Cross-Project Reference Fails
Author: andymatuschak
Created: 2011-10-23 16:38:02+00:00
State: open

***Karl Moskowski (kolpanic)** [reported (on Launchpad)](https://bugs.launchpad.net/sparkle/+bug/349103) on' 2009-03-26:*

I've been using a cross-project reference for an internal FW and it
makes builds much easier and the source much cleaner. I don't have to
copy the built FW into my project manually every time I update it.
Instead, Xcode handles it all.

I tried this:
- delete the built Sparkle.framework file and references from my app's Xcode project
- add a reference to Sparkle.xcodeproj into my app project
- add Sparkle.xcodeproj/Sparkle.framework/ as a dependency to my app target, and make sure the FW is a member of the app target
- add Sparkle.xcodeproj/Sparkle.framework/ to the copy files build phase

However, this doesn't build because Xcode builds referenced projects by matching the config names, and:
- the Debug config of Sparkle.xcodeproj is native-only (64-bit in this case), and my app is 32-bit-only
- the Debug & Release configs don't support GC and my app requires it

I was able to work around it by removing the ARCHS line from
ConfigCommonDebug.xcconfig (per bug #304674) and adding
GCC_ENABLE_OBJC_GC = supported to ConfigFramework.xcconfig.

Would there be any drawback to doing this in the main branch? Is
GCC_ENABLE_OBJC_GC ignored with the 10.4 SDK?