• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Framework development and Garbage collection required option?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework development and Garbage collection required option?


  • Subject: Re: Framework development and Garbage collection required option?
  • From: Bill Bumgarner <email@hidden>
  • Date: Wed, 12 Dec 2007 10:22:08 -0800

On Dec 12, 2007, at 1:30 AM, Brad Barclay wrote:
Unfortunately, at the onset of development I forgot to enable the garbage collection in the project build configuration, so I decided to turn it on (setting it to "required"). Unfortunately, doing a full clean and recompiling the release build results in 72 instances of the following three errors:

cc1obj: error: /Library/Caches/com.apple.Xcode.501/ SharedPrecompiledHeaders/SyncSimulationFramework_Prefix- gctbdyvwrkeynthgtwdbgqtqzaxr/SyncSimulationFramework_Prefix.pch: No such file or directory
cc1obj: error: one or more PCH files were found, but they were invalid
cc1obj: error: use -Winvalid-pch for more information


I've checked, and the directory does exist, however the "PCH" file inside is actually named "SyncSimulationFramework_Prefix.pch.gch" (note the appended extension).

Try blowing away the cache entirely. That might fix this issue. But probably not.


I just tested this against a simple Cocoa framework; build without GC, then build with GC only. It worked fine. This indicates that there is something in the configuration of your project triggering this behavior.

Is this a known limitation? Is there a fix for this, or should I just add retain/release messages to my code and use the "Supported" GC setting, and then use "Required" for the applications that rely on this framework?

This appears to be two bugs; one in your project's configuration and one in the absolutely baffling error message spit out by the compiler / Xcode.


If your application and GC'd unit tests are the only ones that will use the framework, you can safely build with "gc supported" and ignore all retain/release/autorelease calls. It'll leak like a sieve if ever used in non-GC, of course.

b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Framework development and Garbage collection required option?
      • From: Brad Barclay <email@hidden>
References: 
 >Framework development and Garbage collection required option? (From: Brad Barclay <email@hidden>)

  • Prev by Date: Re: How to make a program look for dylibs other than /usr/local/lib?
  • Next by Date: How to add classes to Xcode 3.0
  • Previous by thread: Framework development and Garbage collection required option?
  • Next by thread: Re: Framework development and Garbage collection required option?
  • Index(es):
    • Date
    • Thread