• 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: Project missing build settings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Project missing build settings


  • Subject: Re: Project missing build settings
  • From: Chris Espinosa <email@hidden>
  • Date: Mon, 19 Oct 2009 08:17:07 -0700


On Oct 19, 2009, at 3:23 AM, Jack Nutting <email@hidden> wrote:

I've got a strange situation running Xcode 3.1.4 on Leopard, where
different projects have different sets of available build
configuration settings in the project info panel.  I have, for
example, two iPhone projects, created about a week apart.  The first
one contains the following list of groupings in the project info
panel's Build tab:

Architectures
Build Locations
Build Options
Code Signing
Compiler Version
Deployment
Kernel Module
Linking
Packaging
Search Paths
Unit Testing
Versioning
GCC 4.2 - Code Generation
GCC 4.2 - Language
GCC 4.2 - Preprocessing
GCC 4.2 - Warnings
Interface Builder Compiler - Interface Builder Compiler

The second project, created about a week later, with the same version
of Xcode, contains all of the above, except for the GCC groupings!
Instead, a handful of GCC options (GCC_C_LANGUAGE_STANDARD,
GCC_WARN_ABOUT_RETURN_TYPE, GCC_WARN_UNUSED_VARIABLE) show up in a
"User-Defined" grouping at the bottom.

Neither of these projects have I "messed with" in any way.  Both are
set up to compile with GCC 4.2, the default setting.  Any idea what
can cause this discrepancy?

The likely cause is that the second project is configured with a Base SDK of an iPhone SDK that does not exist on your system.


This can happen after upgrading or reinstalling Xcode. Some versions of the iPhone SDK installers don't have older SDKs,

The Base SDK setting (usually on the Target, but occasionally on the Project) determines where Xcode gets its compiler configuration from. If the base SDK is invalid, Xcode can't figure out what compiler to use, so it can't get the list of appropriate build settings for that compiler.

Your target may actually compile correctly if you've set an override Active SDK in the Overview popup. Since this overrides the invalid Base SDK setting, Xcode actually builds with a complete set of settings. But the Build Settings panel shows the actual setting values before the override is applied, so it shows the unresolved compiler settings as missing.

Set the Base SDK in the Target to a valid iPhone SDK and the missing settings should appear.

Chris
_______________________________________________
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: Project missing build settings
      • From: Jack Nutting <email@hidden>
References: 
 >Project missing build settings (From: Jack Nutting <email@hidden>)

  • Prev by Date: Project missing build settings
  • Next by Date: Understanding diagnostics
  • Previous by thread: Project missing build settings
  • Next by thread: Re: Project missing build settings
  • Index(es):
    • Date
    • Thread