License requirements for framework built on JUCE

Currently, all I see in the JUCE license is that if software is based on JUCE and it’s open source, then it can be created with the GPL license.

I don’t see anything relevant to creating a framework that incorporates JUCE that can be used in a closed-source application, even if the client has a license for JUCE. I have a framework I’m building that I’l like to make open source, but I don’t want to require that the framework be used in only open-source GPL projects. Is this a possibility, or is GPL the only way to go?

1 Like