[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Distributing pygame games for non-Windows platforms
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Distributing pygame games for non-Windows platforms
- From: "Brian Fisher" <brian@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 28 Apr 2007 19:15:13 -0700
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Sat, 28 Apr 2007 22:15:24 -0400
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Q1Os8S23LMJUa4m39Vaytl8mmT9Nsp20xOIrmCndkzB5GR5JlKdEfK5+IN+93lQB8j66mDvK0Uq2VqZT5kSNb8oZtvc25vq0cxCXZL+xeQifvSqlqFlWHdofcNTTo/4clHYhkOQ1/2CdTN5RqYWI91pPvaX7oU9PJYU0BpiXT0E=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=e62CZ9rWHtBjVbm+dVv0t2t87LAEgNl0QWi8aJIe90xNDu7eBbMkyWvHSekm9YtenOaLlLhmP3KbltztE+cvssUgQk1WdOps5PvMWUXcC07X0gPpS+3Cr9Vti1ZLwQO84WVxrAPRb4ENPbxINWpnyuZgVqDsBagNUT/FbcOVB7A=
- In-reply-to: <4633FDE5.2020009@xepher.net>
- References: <834968.99622.qm@web35402.mail.mud.yahoo.com> <4633B9D8.80602@xepher.net> <200704281723.36429.sonicbhoc@gmail.com> <4633FDE5.2020009@xepher.net>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
On 4/28/07, Kris Schnee <kschnee@xxxxxxxxxx> wrote:
Pygame itself uses the LGPL. According to
<http://en.wikipedia.org/wiki/LGPL>, building a standalone executable
that _uses_ Pygame without including a modified version of Pygame still
requires that it "be possible for the software to be linked with a newer
version of [Pygame]." It's possible that all that means is, people must
be able to replace the "library" ZIP file that Py2EXE creates -- an act
that doesn't require releasing the source.
Well here's an exceprt from the actual LGPL that talks about meeting
this condition with dynamic linking (there are 4 ways besides dynamic
linking as well, BTW):
----
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a copy
of the library already present on the user's computer system, rather
than copying library functions into the executable, and (2) will
operate properly with a modified version of the library, if the user
installs one, as long as the modified version is interface-compatible
with the version that the work was made with.
----
it seems to my that py2exe's library.zip thing would meet the terms of
that language (the executable links to an already present copy of
pygame in the zip). Without knowing exactly how pyinstaller's single
file works, I would guess that it would not meet the terms (I assume
it has copied library functions into the executable)