Changed page "FAQ" by giovannibajo from 27.244.106.158*
Page URL: <http://www.pyinstaller.org/wiki/FAQ>
Diff URL: <http://www.pyinstaller.org/wiki/FAQ?action=diff&version=11>
Revision 11
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 10)
+++ FAQ (version: 11)
@@ -17,6 +17,6 @@
1. '''Is there a way to open a ticket?''' [[BR]] You may open a ticket login
as openticket and using that same information as the password.
1. '''With !PyInstaller, I don't get Windows XP themes in my application with
wxPython! ''' [[BR]] Make sure you are using at least !PyInstaller 1.3, and
that you are building a windowed mode executable (pass {{{-w}}} to
{{{Makespec.py}}}).
- 1. '''What about {{{.egg}}} files?''' [[BR]] !PyInstaller trunk fully
supports .egg files: they are bundled as-is. In one-dir mode, you will see them
on the filesystem; in one-file mode, they will be unpacked within the temporary
directory along with dynamic libraries. This is actually a workaround, but it
is better than nothing, and makes sure that all .egg features (eg: entry
points, pkg_resources, etc.) work correctly. Notice that PyInstaller **does**
inspect .egg files at build-time and correctly look for dependencies they bring
in.
+ 1. '''What about {{{.egg}}} files?''' [[BR]] !PyInstaller trunk fully
supports .egg files: they are bundled as-is. In one-dir mode, you will see them
on the filesystem; in one-file mode, they will be unpacked within the temporary
directory along with dynamic libraries. This is actually a workaround, but it
is better than nothing, and makes sure that all .egg features (eg: entry
points, pkg_resources, etc.) work correctly. Notice that !PyInstaller
'''does''' inspect .egg files at build-time and correctly looks for
dependencies they have.
1. '''What about [http://peak.telecommunity.com/DevCenter/PkgResources
pkg_resources]?''' [[BR]] {{{pkg_resources}}} is currently not supported by
!PyInstaller. This means that an application using a library which uses the the
{{{pkg_resources}}} API will probably not work out of the box. The only
situation in which it works is when it's being used on .egg files (see above).
1. '''Under Linux, I get runtime dynamic linker errors, related to libc. What
should I do?''' [[BR]] The executable that !PyInstaller builds is not fully
static, in that it still depends on the system libc. Under Linux, the ABI of
GLIBC is backward compatible, but not forward compatible. So if you link
against a newer GLIBC, you can't run the resulting executable on an older
system. The solution is to compile the bootloader on the ''oldest'' system you
have around, so that it gets linked with the oldest version of GLIBC. Then, you
can copy the bootloader binaries ({{{support/loader/*}}}) into your development
system and run {{{Build.py}}} there.
-------8<------8<------8<------8<------8<------8<------8<------8<--------
* The IP shown here might not mean anything if the user is behind a proxy.
--
Pyinstaller <http://www.pyinstaller.org>
PyInstaller Project
This is an automated message. Someone at http://www.pyinstaller.org
added your email address to be notified of changes on Pyinstaller.
If it was not you, please report to http://www.pyinstaller.org.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---
