written by: NothanUmber
So, a hypothetical commercial plugin could use all headers that are in the include directory of the EigenD binary delivery (even though some of them have a GPL3 header) but not additional things from the GPL EigenD tree (that are not occuring in the EigenD binary delivery), right?Quick question, where we reference sources in the main EigenD build, do we need to copy them into our contributions? It seems that only a subset of the headers are shipped with the releases? (eg. I'm using plg_stk/src/OnePole.h in the noise agent). If not, then how do they get picked up in the build of the agent?
D
Yes, you'll have to copy it.
We are trying to build a supportable API, and we can't include everything in that API. Not everything that's currently in the piw library will stay there over the next few releases.
You are welcome to use anything in the source tree for reference, and copy anything you need though.
jim
Quick addition to that - that's very true if you're working with the GPLv3 and putting your code back into the public domain, but bear in mind that it's not true if you want to subsequently sell the Agent under any other license. Sorry to be a license bore, just don't want anyone to make that mistake and live to regret it, it's easily done and very tedious in the event (re-implementing a pile of code from scratch when one has already used a perfectly good GPL version of the same code is one of life's less inspiring activities).
With that proviso, go ahead and copy them to your hearts content. No point in reinventing the wheel.
John
So, a hypothetical commercial plugin could use all headers that are in the include directory of the EigenD binary delivery (even though some of them have a GPL3 header) but not additional things from the GPL EigenD tree (that are not occuring in the EigenD binary delivery), right?
Please log in to join the discussions
UK
