I have one question on using Oxygen Icons in my proprietary software

Theo Cai theo.cai at outlook.com
Tue Nov 19 05:27:54 GMT 2019

Hi Jonathan:

Thank you for your suggestions. I will add information - 'credit KDE' in help documents and associated readme file.


在 2019/11/18 19:50, Jonathan Riddell 写道:
Yes the steps you describe should be enough to legally distribute the Oxygen icons with your application.  You should credit KDE as well.  Interactive GUI apps often have a Help menu item to do it.

Good luck with it

Jonathan Riddell

On Fri, 15 Nov 2019 at 07:51, Theo Cai <theo.cai at outlook.com<mailto:theo.cai at outlook.com>> wrote:

Hello KDE Webmasters:

I am developing one application running in PC which needs some icons. I find these great icons from following website:


According to information in link above I find the license information:



It looks like that I can use these icons in my application(closed source and non-free software) if I use these icons as the way indicated in the license:


Use in Applications

Oxygen Icons can be used with computer programmes, including proprietry applications or ones covered by non-GPL licences.
In your source code you must include a copy of the LGPLv3 licence text making it clear which files it applies to and point to http://www.kde.org/. You must also include the SVG of the relevant icons even if they are not used by the application (this is the preferred modifiable form).
With your application binary you must also include a copy of the LGPLv3 licence text making it clear which files it applies to and point to http://www.kde.org/. If you do not include the icon SVGs you must make it clear how the user can get them (for a free software application this will be as part of the source code).
There is one license issue to watch for with proprietary applications, you should not embed the icon into the application binary. This happens if you use Qt resource files or .net linking. This would mean the whole application is now LGPL. Instead you should keep the .png as a separate file and load it at runtime. (There are provisions in the LGPL for allowing this if you have a mechanism to relink to a modified version but most applications do not have such a mechanism).


Now, I just use some icons(less than 20 icons, format is png) in my software. I also include the LGPLv3 file, the license information(fetched from: https://techbase.kde.org/Projects/Oxygen/Licensing) in my application package.

Are these steps are enough for me to publish my software in market? Do you have any suggestions?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-www/attachments/20191119/2b7c51c2/attachment.html>

More information about the kde-www mailing list