Thanks for the input. From what I'm aware of with LGPL in the C world is that if you modify the source to "libLib" and then compile "libLib.so" and link to "libLib.so" using your app, you're safe. But if you compile "libLib" as a statically linked library, and link it into your application so that they are all combined into a single file, you have to release your source. I'm not sure that my understanding is correct, but if it is, I was wondering if it applies in a similar means to a swf file. Thanks again.
Dan
On 4/4/06, Ralf Bokelberg <[EMAIL PROTECTED]> wrote:
Afaik only changes to the library itself have to be published under the LGPL. That's the reason for the existence of the LGPL.
Cheers,
Ralf.On 4/4/06, Dan Shryock < [EMAIL PROTECTED]> wrote:I just wanted to ask the list what its thoughts were about the requirements of the LGPL license when being compiled into a swf. I am currently considering porting the JSON-RPC-Java client library (LGPL, written in _javascript_) to actionscript 3. I have no concerns about releasing the source of the ported library, but if I were to build an application in Flex2, and it were compiled into the swf, would I be obligated to release all other source for my application? If so, would the only way arround this be to build some separate swf which contains only the LGPL library, and an application swf which links to the other to gain access to the library? I appreciate any insight on this issue.
Dan
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
