Martin v. Löwis wrote: > 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. > > So this is only an option if "a copy of the library [is] already > present on the user's computer system". This may work for Linux, > but not for Windows, or Solaris (not sure about OSX).
I think it's just trying to say dynamic rather than static linking, not that the library has to be a pre-existing one. The important thing is that the library can be updated just by replacing a file, without having to re-link the executable. So Windows DLLs qualify, as far as I can see. -- Greg _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
