• 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: Inheriting 'Preprocessor Macros' from Project settings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Inheriting 'Preprocessor Macros' from Project settings


  • Subject: RE: Inheriting 'Preprocessor Macros' from Project settings
  • From: "Yuichi Kuroda" <email@hidden>
  • Date: Thu, 19 Mar 2009 14:04:45 -0400
  • Thread-topic: Inheriting 'Preprocessor Macros' from Project settings

Thanks, I got it resolved. The fields for 'preprocessor macros' were still in the Target info windows, even if they were empty. I got rid of those and the project settings took effect.

Yuichi Kuroda


-----Original Message-----
From: Jean-Daniel Dupas [mailto:email@hidden]
Sent: Thursday, March 19, 2009 11:00 AM
To: Fritz Anderson
Cc: Yuichi Kuroda; email@hidden
Subject: Re: Inheriting 'Preprocessor Macros' from Project settings


Le 19 mars 09 à 18:45, Fritz Anderson a écrit :

> On 19 Mar 2009, at 12:04 PM, Yuichi Kuroda wrote:
>
>> Hi I'm trying to use macros that are defined in the 'Preprocessor
>> Macros' field in the main project setting throughout my source
>> files compiled in various Targets, but they aren't being recognized
>> unless I set the macros in every Target setting. I've read
>> somewhere that Project settings are inherited by all Targets if a
>> particular field is not set in the Target. Anyone know why this
>> isn't working?
>
> 1. In the Project Info window, look at the configurations pop-up.
> Make sure you select all configurations (if that is what you mean)
> when you set the macros.
>
> 2. In the Target Info windows, make sure there is no overriding
> setting for preprocessor macros. If the label for the setting is in
> bold, then the target overrides it, even if the content of the
> setting in the target is blank. Again, check this with all
> configurations set.
>
> 3. If targets need to supplement, not override, the project setting,
> use $(VALUE) to pull the project's setting into the target.

IIRC you should use $(inherited) instead of $(VALUE) to pull the
project's setting.




 _______________________________________________
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: 
 >Inheriting 'Preprocessor Macros' from Project settings (From: "Yuichi Kuroda" <email@hidden>)
 >Re: Inheriting 'Preprocessor Macros' from Project settings (From: Fritz Anderson <email@hidden>)
 >Re: Inheriting 'Preprocessor Macros' from Project settings (From: Jean-Daniel Dupas <email@hidden>)

  • Prev by Date: Re: Inheriting 'Preprocessor Macros' from Project settings
  • Next by Date: Info.plist preprocessing and header dependency
  • Previous by thread: Re: Inheriting 'Preprocessor Macros' from Project settings
  • Next by thread: Info.plist preprocessing and header dependency
  • Index(es):
    • Date
    • Thread