Using scripting #if define symbols in DLLs

Question

Hi,

I created a new Debug DLL and imported it into the Plugins folder. Everything works fine except that scripting define symbols which are defined in Unity aren't picked up inside the DLL. The DLL code contains this:

 public static class Debug
 {
     public static void Check()
     {
 #if !DEBUG_OUTPUT_OFF
         UnityEngine.Debug.Log("Debug output is ON");
 #else
         UnityEngine.Debug.Log("Debug output is OFF");
 #endif
     }
 }

In Unity, I've set DEBUG_OUTPUT_OFF for the current build platform, but calling this:

         Debug.Check();
 
 #if DEBUG_OUTPUT_OFF
         Debug.Log("Output seems to be off in Unity");
 #endif

...produces this output:

 Debug output is ON
 
 Output seems to be off in Unity

So is there a way to make Unity's scripting define symbols available to DLL code?

Answer 1

Answer by Dave-Carlile · Jul 23, 2015 at 12:53 PM

The defines are compile time things. Once you compile your code, they don't exist, and the code that they filter out doesn't exist.

Your plugin dlls are already compiled outside of Unity. That means they don't and can't know anything about compile conditions you've set up.

What are you trying to do?

Add comment · Show 2 · Share

MSDev002 · Jul 23, 2015 at 05:26 PM 0

Share

I'm trying to make the DLL code sensitive to a define symbol defined in Unity. I'm sure that in a previous project, exactly this kind of setup worked, with some small additions. I guess I need to rebuild the DLL with the same symbols every time I Build&Run through Unity? $$anonymous$$aybe by adding something to the build postprocess? Or preprocess?

Dave-Carlile · Jul 26, 2015 at 01:46 AM 0

Share

Yes you would need to rebuild the dll. I know you can something post process with Unity, but I'm not sure about pre-process.

Using scripting #if define symbols in DLLs

1 Reply

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions