Swift Compiler Flags Wont affect Objective-C code

Question

under Active Compilation Conditions i have added a new flag (for debug only) called SOMEFLAG. the check is implemented like so and works great:

#if SOMEFLAG
   print("SOMEFLAG is true");
#endif

it actually prints like i would expect. now, i need to examine the same flag from Objective-C class and it never evaluates to true. any idea why? should i make this flag in other way? in general my goal is to be able to detect when it is executed from another target, the build is triggered from the cli. if there is other way that less limiting i would like to know.

thanks!

See if this is helpful: stackoverflow.com/questions/56878455/… — Anatoli P
– Anatoli P, Commented Dec 10, 2019 at 3:54

gmw · Accepted Answer · 2019-12-09 13:18:04Z

1

In Objective-C (and other C-like languages that use a preprocessor) the canonical way to check whether a symbol is defined would be using #ifdef, not #if. There is an #if directive in Objective-C, but it doesn't behave quite the same way as the Swift #if compiler directive.

answered Dec 9, 2019 at 13:18

gmw

4473 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Swift Compiler Flags Wont affect Objective-C code

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related