0

We have our own proprietary software that we are developing for commercial business. We want to sell the software and we do not have any problem in distributing the source code to our customers. Due to the lack of good build infrastructure and complexity of the software, it has become difficult to manage and has lost its readability.

An easy way to manage this is by making use of Kbuild as is done in Linux and U-Boot. This means using (and customizing) Kbuild and Kconfig specific files (and few modified Makefiles) to compile our software.

I went through all the FAQs for GPL v2 (https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html) but I'm not able to make what implications would be of using Kbuild infrastructure in my proprietary software. Can anyone help me in understanding them?

  • 1
    This is a great question? why why this downvoted? please add a comment when you do so. – Philippe Ombredanne Apr 8 '17 at 10:46
2

I'm not able to make what implications would be of using Kbuild infrastructure in my proprietary software.

The reason why you are not able to make what the implications would be is there there are absolutely no implications whatsoever. The Kernel build system is under the same license as the Kernel e.g. the GPL, but the fact that it is GPL or else does not matter here.

Using the Kbuild scripts -- or any other build script -- to build any kind of software has no bearing on the software being built in 99.99% of the cases.

The analogy would be using a text editor to write programs: the license of Microsoft Word does not impact the license of a document you write with Word.

Or the EPL license of the Eclipse IDE does not impact the license of any code written with Eclipse.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.