• 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: Linking errors after upgrading to XCode 3.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking errors after upgrading to XCode 3.2


  • Subject: Re: Linking errors after upgrading to XCode 3.2
  • From: Fritz Anderson <email@hidden>
  • Date: Fri, 2 Jul 2010 09:32:02 -0500

On 1 Jul 2010, at 11:13 PM, Kin Mak wrote:

> I did. I set my Base SDK to "Simulator 3.2". But it did not work.
> I even tried to set it to "Simulator 4.0", it did not work either.

Ah. Then you did not set your _base_ SDK correctly. It should always be a device SDK, never the simulator.

When you want to run on the simulator, use the popup menu in the toolbar to temporarily aim the build/installation at the simulator.

But the Base SDK (SDKROOT) setting, in the project or target Build settings, must always be Device 3.2 or Device 4.0.

	— F

 _______________________________________________
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

References: 
 >Re: Linking errors after upgrading to XCode 3.2 (From: Matt Neuburg <email@hidden>)
 >Re: Linking errors after upgrading to XCode 3.2 (From: Kin Mak <email@hidden>)

  • Prev by Date: Re: force-restarting iPhone apps in Simulator from Xcode 3.2.3/iOS sdk4
  • Next by Date: Re: force-restarting iPhone apps in Simulator from Xcode 3.2.3/iOS sdk4
  • Previous by thread: Re: Linking errors after upgrading to XCode 3.2
  • Next by thread: Build errors with linked static library in iPhone project under xcode 3.2.3
  • Index(es):
    • Date
    • Thread