-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide source code for gcc toolchain #281
Comments
FYI: The PlatformIO documentation explicitly mentions the ARM GNU toolchain: https://docs.platformio.org/en/latest/platforms/heltec-cubecell.html#packages |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a follow-up to #105 (and possibly #80 ).
As per the conditions of the GPL, you're obliged to provide source code for a software that contains GPL code, if requested. It doesn't matter if you modified the original code or not, but if you do, the modifications must be released under the GPL as well.
As the GNU Compiler Collection (gcc) is released under the the GPL, I'm formally requesting the source code for the toolchain downloadable from https://resource.heltec.cn/download/gcc-arm-none-eabi-8-2019-q3-update-linux.tar.gz .
Judging by the file names, it looks like you're distributing the GNU Arm Embedded Toolchain from https://developer.arm.com/downloads/-/gnu-rm#panel7a . If this is the case, I think it would be sufficient to copy the source package from ARM to your download server. This will ensure it remains downloadable when ARM removes the download or the ARM website is inaccessible for some reason.
Nonetheless, I think it would be polite that you mention in your documentation that the CubeCell SDK uses the GNU Arm Embedded Toolchain and link to the ARM website. Maybe also mention that new versions can be downloaded from there, if you want to support this.
Furthermore, I was wondering if you could release the source code for CubeCellflash, CubeCellelftool and flash6601.
As you mentioned in #80 (comment) , these tools contain trade secrets (a custom bootloader?) and you're not ready to release them as open source yet.
Has this changed?
The text was updated successfully, but these errors were encountered: