• 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
Framework development and Garbage collection required option?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Framework development and Garbage collection required option?


  • Subject: Framework development and Garbage collection required option?
  • From: Brad Barclay <email@hidden>
  • Date: Sun, 9 Dec 2007 23:29:15 -0800

Good-day Everyone:

I've started a new project that is being written solely in Xcode 2.0, to be run on OS X 10.5 (this isn't intended to be consumer code; it's part of a scientific simulation environment). It has been designed with a number of common objects, which I decided to put into a framework.

I used the Framework template in Xcode 3.0 to create the Framework, and have created a number of objects. As I intend the simulation to use the new Garbage Collection features, I wrote it without any retain/ release calls.

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).

Building a debug build works fine, as does building if I change the Garbage collection setting to "Supported". I'd included a number of unit tests to the Xcode project to verify the simulation classes, and I'd prefer to be able to run them with full garbage collection (as this is the way the final applications will be built and run).

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?

	Any aid would be gratefully welcomed.

Brad BARCLAY

=-=-=-=-=-=-=-=-=-=
From the Mac OS X Desktop of Brad BARCLAY
E-Mail:  email@hidden     Web:  http://www.jsyncmanager.org

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

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