| |||||||||||||
Plugging into GCCPlugging into GCCPosted Oct 4, 2008 8:44 UTC (Sat) by drag (subscriber, #31333)In reply to: Plugging into GCC by ikm Parent article: Plugging into GCC
If people wanted to make a proprietary plugin to GCC then they would of already done so.
The GCC suite is free software last time I checked, so modifying the GCC source code to communicate with a proprietary hunk of software is something that they can already certainly do. Just as long as they release the GCC portion of the patch under the GPL there is nothing stopping them from having it work with something closed source.
(Log in to post comments)
The question is all about the cost Posted Oct 5, 2008 7:50 UTC (Sun) by khim (subscriber, #9252) [Link] Not so simple. One company should introduce (and support) such modified version of GCC and another unrelated company can then produce proprietary plugin (if they will be related court can declare both the part of the cartel created to circumvent the GCC). And this makes the whole scheme totally unrealistic: second company is doing it's business on the basis of code produced by someone who has NO obligations to that company AND is not supported upstream... Very flacky foundations. And GCC developers will not tolerate such abuse: where kernel developers are in unenvious situation where they can punish abusers only at the expense of users (there are no way to use nVidia cards except by using binary module) GCC works just fine without any such proprietary blobs... Sorry but to distribute proprietary plugin to GCC today is not hard. It's very hard... FSF will like to keep it this way - what's so strange about this?
|
|||||||||||||