Licensing a project that can conditionally compile in support for juce?

I’m working on an ultra top secret audio library, and I’m thinking about adding optional support for hosting plugins with juce via conditional compilation. Basically all juce code would be wrapped in ifdefs, like so:

#ifdef SUPPORT_JUCE
    #include <juce_core/juce_core.h>
    // do juce specific stuff
#endif

My question is, would it be legal for me to permissively license the version of my library compiled without juce support? Obviously the version with juce support would be subject to all of juce’s licensing restrictions, but if the juce code never gets compiled in, then it’s the same as if it was never there in the first place, no? So could I license that version of my project as if it didn’t depend on juce (because it wouldn’t)?
My intuition tells me that this would be okay, but the fact that there would still be references to juce in my source code makes me wonder…

I’ve tried looking for the answer on the web, but suprisingly nothing comes up, even for very general queries about software licensing and conditional compilation

I am not a lawyer.

I would say it is fine. Under AGPLv3, the link happens when you compile your library with JUCE.

1 Like

Thanks for the response

Yeah I think I’ll just go for it. If Jules sues me I’ll just fake my death and escape to the Zihuatanejo or something

1 Like

It is PACE now :melting_face: But I think you will be fine.