1

After reading this stackoverflow post, I tried to introduce macros in my project. I have the following code in a sample macOS CommandLine tool.

#if         ELDIABLO
NSLog ("ELDIABLO macro detected!")
#else
NSLog ("ELDIABLO macro not detected!")
#endif

The ELDIABLO macro is declared in Target->BuildSettings->SwiftCompiler/OtherSwiftFlags (prefixed with -D).

This works.

SwiftMacros[73110:12048088] Detected ELDIABLO macro!!

Now, when I transferred the same concept to my original project it doesn't work. I always get

ELDIABLO macro not detected!

According to another stackoverflow post, the macros should be defined in Target->BuildSettings->SwiftCompiler/ActiveCompilationConditions (without -D prefix). I tried that too, but didn't work.

What's wrong here? What am I missing?

I'm using Xcode 13.4.
My project structure: One target (the app) dependent on many other targets (static libs). All macro settings are applied to the app target (not to the static libs).

NightFuryLxD
  • 847
  • 5
  • 15

2 Answers2

1

I was setting the macro in the app target, but the code which uses macro is one of the other targets i.e static libs, though the static libs targets are added as a dependency for the app target.

After adding the macro to the static lib target, it works.

NightFuryLxD
  • 847
  • 5
  • 15
0

That means the macro didn't find your "Condition setting", ex: ELDIABLO

So now you need to open your Project/[Your in-use target]/Build Settings. Then, search the setting with the keyword: "active compilation". And, put your CONDITION_CONFIG here. One line for one CONDITION_CONFIG.

Check image below:Macro key setting

Neklas
  • 504
  • 1
  • 9
  • I initially added the macro in 'OtherSwiftFlags', but later moved it to 'ActiveCompilationCondition' after checking out other stackoverflow posts (mentioned in question). It didn't work. – NightFuryLxD Sep 12 '22 at 11:27
  • @NightFuryLxD Could you attach your screenshot of the current config? Update your question then we can see it. – Neklas Sep 13 '22 at 03:24
  • Found the issue. I was setting the macro in the app target, but the code which uses the macros is in one of the static libs. When I added macros to that target (static lib), its working. Thank you for your time. – NightFuryLxD Sep 13 '22 at 05:08