License to use for including same header file both in GPL and Proprietary application [closed]

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 5 years ago.

Improve this question

I have a small C header file (i wrote it) which contains only some #define values. I want to #include this header file both in a proprietary application and a GPL application.

I don't mind the header file goes public along with the GPL app. But I can't provide sources of proprietary application to public.

What license should I use for my header file? For example

//
// gplapp.c
#include "/home/project/myheader.h"
int main () {......}

and

//
// proprietaryapp.c
#include "/home/project/myheader.h"
int main () {......}

-

Makefile: build both gplapp.c and proprietaryapp.c

Answer 1

I'm not sure if I understand your problem fully, however, as long as the code of the header file is yours, you can license it this way and the other time that way. As it's your code, you can license it under any license you want to, which includes multiple licenses in different projects.

If you are the sole author, you're in control, unless you have given away that right.

Answer 2

Put the GPL in the header. Make it clear that you own the copyright and may license it under other licenses.

Since only the copyright owner has the right to make you comply with the GPL you just have to promise to not sue yourself for using your GPLed code in a proprietary app and not distributing the source.