GNU General Public License, version 2
Kernel Developers:
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
ROM Developers:
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to the OEM source page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel:
Source: android_kernel_sony_msm8x60 - Linked directly to where your source is located, ie; github, bitbucket
Compiler: Linaro GCC 4.8 ToolChain - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
Click to expand...
Click to collapse
GNU General Public License, version 2 is strictly enforced by XDA, to prevent legal issues.
We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2
XDA-Developers and the GPL
~Toledo_JAB
Forum Specific Moderator
Related
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator