Mixing GPL and non-GPL Frameworks in software

Question

Hi, so heres my issue. I'm currently developing a program: Lets call it "Program A". There is an existing framework, call it "Framework A", and that framework is GPL licensed.

I have also developed another framework, call it "Framework B", this framework does not depend on Program A, or on Framework A. It can stand alone and be used in multiple situations.

Program A uses, and will be distributed with both Framework A, and Framework B. I understand that because of this I am required to make Program A GPL licensed as well.

My questions is if I am to distribute these three together, is Framework B required to be GPL licensed? I would very much like to keep it closed-source.

I understand that it would be best for me to contact an attorney for figuring this out, I would just like to hear other people's experiences and knowledges with this before I proceed.

Answer 1

If the two programs' source do not touch and they are not linked together in anyway(as in, they will run without the other) then you should definitely be in the clear.

Note, I am not an attorney.

Answer 2

Essentially, you will have a GPL-ed program (Program A) calling a closed-source library (Framework B). As far as the GPL goes, I don't think there is a problem with this. The non-GPL code is not using GPL code, so I don't think the GPL has any say in how you license Framework B. If Framework B calls some functions from either Framework A or Program A, then you have an entirely different situation on your hands. The (so-called) "viral" aspect of the GPL only flows upstream (from a GPL library to the code that calls it) and doesn't effect independent "siblings" in the hierarchy as you have.

Of course, IANAL, YMMV, and all the standard disclaimers apply.