How to define a preprocessor symbol in Xcode

Objective CXcodeC Preprocessor

Objective C Problem Overview


Is it possible to set a symbol for conditional compilation by setting up properties in an Xcode project?

My aim is to to create a symbol that is available to all files, without having to use import/include, so that a set of common classes can have a special behavior in some projects. Like the following, but with my own symbols.

#if TARGET_IPHONE_SIMULATOR
    ...
#endif

Objective C Solutions


Solution 1 - Objective C

Go to your Target or Project settings, click the Gear icon at the bottom left, and select "Add User-Defined Setting". The new setting name should be GCC_PREPROCESSOR_DEFINITIONS, and you can type your definitions in the right-hand field.

Per Steph's comments, the full syntax is:

constant_1=VALUE constant_2=VALUE

Note that you don't need the '='s if you just want to #define a symbol, rather than giving it a value (for #ifdef statements)

Solution 2 - Objective C

You don't need to create a user-defined setting. The built-in setting "Preprocessor Macros" works just fine. alt text

If you have multiple targets or projects that use the same prefix file, use Preprocessor Macros Not Used In Precompiled Headers instead, so differences in your macro definition don't trigger an unnecessary extra set of precompiled headers.

Solution 3 - Objective C

As an addendum, if you are using this technique to define strings in your target, this is how I had to define and use them:

In Build Settings -> Preprocessor Macros, and yes backslashes are critical in the definition:

APPURL_NSString=\@\"www.foobar.org\"

And in the source code:

objectManager.client.baseURL = APPURL_NSString;

Solution 4 - Objective C

You can use the *_Prefix.pch file to declare project wide macros. That file is usually in you Other Sources group.

Solution 5 - Objective C

It's under "GCC 4.2 Preprocessing" (or just put "prepro" in the search box)...

...however, for the life of me I can't get it to work.

I have my standard Debug and Release configurations, and I want to define DEBUG=1 in the debugging configuration. But after adding it as a value:

(in the settings window) > Preprocessor Macros : DEBUG=1

#if DEBUG
    printf("DEBUG is set!");
#endif 

...never prints/gets called. It's driving me crazy...

Solution 6 - Objective C

For Xcode 9.4.1 and C++ project. Adding const char* Preprocessor Macros to both Debug and Release builds.

  1. Select your project

select project

  1. Select Build Settings

select build settings

  1. Search "Preprocessor Macros"

search1 search2

  1. Open interactive list

open interactive list

  1. Add your macros and don't forget to escape quotation

add path

  1. Use in source code as common const char*

    ...
    #ifndef JSON_DEFINITIONS_FILE_PATH
    static constexpr auto JSON_DEFINITIONS_FILE_PATH = "definitions.json";
    #endif
    ...
    FILE *pFileIn = fopen(JSON_DEFINITIONS_FILE_PATH, "r");
    ...
    

Solution 7 - Objective C

In response to Kevin Laity's comment (see cdespinosa's answer), about the GCC Preprocessing section not showing in your build settings, make the Active SDK the one that says (Base SDK) after it and this section will appear. You can do this by choosing the menu Project > Set Active Target > XXX (Base SDK). In different versions of XCode (Base SDK) maybe different, like (Project Setting or Project Default).

After you get this section appears, you can add your definitions to Processor Macros rather than creating a user-defined setting.

Solution 8 - Objective C

You can duplicate the target which has the preprocessing section, rename it to any name you want, and then change your Preprocessor macro value.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSteph ThirionView Question on Stackoverflow
Solution 1 - Objective CBen GottliebView Answer on Stackoverflow
Solution 2 - Objective CcdespinosaView Answer on Stackoverflow
Solution 3 - Objective CStickleyView Answer on Stackoverflow
Solution 4 - Objective CchunkyguyView Answer on Stackoverflow
Solution 5 - Objective ChEADcRASHView Answer on Stackoverflow
Solution 6 - Objective CPetr JavorikView Answer on Stackoverflow
Solution 7 - Objective CMark24x7View Answer on Stackoverflow
Solution 8 - Objective CkslcamView Answer on Stackoverflow