I have never heard that you needed to supply the entire tool chain, just the source for the code that you run in your product. I'm strictly a beginner at such things, though, so take what I say with a kilo or so of salt...
> -----Original Message----- > From: geda-user-boun...@moria.seul.org > [mailto:geda-user-boun...@moria.seul.org] On Behalf Of John Griessen > Sent: Wednesday, October 06, 2010 12:21 PM > To: gEDA user mailing list > Subject: Re: gEDA-user: GPLv3 question > > On 10/06/2010 10:30 AM, John Doty wrote: > > You don't need to deliver *any* source code unless it is > requested by the user. > > OK. Let me rephrase that to, > > "What would I need to make available to comply with GPLv3 for > a GPLv3 library delivered as part of an open hardware system?". > > I'm wanting to clarify the difference between GCC used to > make the system's delivered code and > libopenstm32 used to make the system's delivered code, where > parts of libopenstm32 are included in the output. I'm > thinking I would need to make available libopenstm32 source, > but not GCC source. > > Eh? > > JG > > > _______________________________________________ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user