legal-notice.txt 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. [[legal-info]]
  4. Legal notice and licensing
  5. ==========================
  6. Complying with open source licenses
  7. -----------------------------------
  8. All of the end products of OpenADK (toolchain, root filesystem, kernel,
  9. bootloaders) contain open source software, released under various licenses.
  10. Using open source software gives you the freedom to build rich embedded
  11. systems, choosing from a wide range of packages, but also imposes some
  12. obligations that you must know and honour.
  13. Some licenses require you to publish the license text in the documentation of
  14. your product. Others require you to redistribute the source code of the
  15. software to those that receive your product.
  16. The exact requirements of each license are documented in each package, and
  17. it is your responsibility (or that of your legal office) to comply with those
  18. requirements.
  19. Complying with the OpenADK license
  20. ----------------------------------
  21. OpenADK itself is an open source software, released under the
  22. http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General Public
  23. License, version 2] or (at your option) any later version.
  24. However, being a build system, it is not normally part of the end product:
  25. if you develop the root filesystem, kernel, bootloader or toolchain for a
  26. device, the code of OpenADK is only present on the development machine, not
  27. in the device storage.
  28. Nevertheless, the general view of the OpenADK developer is that you should
  29. release the OpenADK source code along with the source code of other packages
  30. when releasing a product that contains GPL-licensed software.
  31. This is because the
  32. http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU GPL]
  33. defines the "'complete source code'" for an executable work as "'all the
  34. source code for all modules it contains, plus any associated interface
  35. definition files, plus the scripts used to control compilation and installation
  36. of the executable'".
  37. OpenADK is part of the 'scripts used to control compilation and
  38. installation of the executable', and as such it is considered part of the
  39. material that must be redistributed.
  40. Keep in mind that this is only the OpenADK developer opinion, and you
  41. should consult your legal department or lawyer in case of any doubt.