Suppose I have some project of which I own the code. It has a library which is licensed under Apache 2.0 (but that shouldn't influence this). So I can choose if I want to release the code using GPL, Apache 2.0 (or similar) or make it a closed source project.
As there is quite some code, I want to build the documentation using doxygen, which is licensed under GPLv2.
Do I now have to publish under GPLv2 (or any equivalent license) if I choose to publish my code? The only thing related to doxygen is the .doxyfile
to build the documentation.
Edit:
This is different to Using output of GNU GPL software in commercial purposes as I am not asking if the resulting documentation is subject to GPL (which is clearly not the case).
What I am asking is: Does the process of me tayloring parts of my code (in this case the comments and said .doxyfile
) for specific use with said GPL software force me to make my code (not the documentation) GPL as well? It seems wierd if it would, but GPL is a bit confusing to me.