Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Can I use CUETools in a commercial project? (Read 2056 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Can I use CUETools in a commercial project?

Hi guys,

I would like to use the ripping functionality of CUETools in a commercial
I'm a bit unsure about the licenses:
on sourceforge, dual licensing (GPL and LGPL) is mentioned:
http://sourceforge.net/projects/cuetoolsnet/
in the source code, only the GPL license is mentioned:
http://sourceforge.net/p/cuetoolsnet/code/...ols/License.txt

Could you please confirm whether it's (also) under LGPL and thus can be used in a commercial project?
Are all components of the project under the same license?

I would only need the .NET libraries - link them at compile time and ship them with my application in an msi.

Thanks a lot!
Chris
 

Can I use CUETools in a commercial project?

Reply #1 –
Sorry for late reply.
As a whole, CUETools and CUERipper are licensed under GPL;
Component libraries written by me are dual-licensed under LGPL.
Unfortunately, i have no control over licenses of some other open-source projects used by CUETools and CUERipper;
Taglibsharp is LGPL as far as i know; Bwg.* modules taken from BwgBurn project can be a problem, because the project is licensed under GPL. You might have to replace them or ask their authors about using them.
CUETools 2.1.6