From e5c1eb746cc02b0bda04189fd650cb640a6ac41d Mon Sep 17 00:00:00 2001 From: Paul Sokolovsky Date: Sat, 13 Jun 2015 23:49:10 +0300 Subject: [PATCH] README: Add "License" section. --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index 0bf5db6..270b5a9 100644 --- a/README.md +++ b/README.md @@ -127,3 +127,23 @@ Additional configuration You can build a statically linked toolchain by uncommenting `CT_STATIC_TOOLCHAIN=y` in the file `crosstool-config-overrides`. More fine-tunable options may be available in that file and/or Makefile. + +License +======= + +esp-open-sdk is in its nature merely a makefile, and is in public domain. +However, the toolchain this makefile builds consists of many components, +each having its own license. You should study and abide them all. + +Quick summary: gcc is under GPL, which means that if you're distributing +a toolchain binary you must be ready to provide complete toolchain sources +on the first request. + +Since version 1.1.0, vendor SDK comes under modified MIT license. Newlib, +used as C library comes with variety of BSD-like licenses. libgcc, compiler +support library, comes with a linking exception. All the above means that +for applications compiled with this toolchain, there are no specific +requirements regarding source availability of the application or toolchain. +(In other words, you can use it to build closed-source applications). +(There're however standard attribution requirements - see licences for +details).