The phrase "in the right place" is a bit too vague for me at the moment. If you can provide more details I can try that.
Adding --debug and --console results in a traceback complaining that "getopt.GetoptError: option --console not recognized". My guess would be that this is because on Windows --console is the default. However, if I eliminate --console from the command line, no diagnostics appear in the Cmd Prompt window. Has this been tested on Windows or only on *nix?
What appears in the text output is:
W: no module named posix (conditional import by os)
W: no module named org (top-level import by copy)
W: no module named posix (delayed, conditional import by iu)
W: no module named pwd (delayed, conditional import by posixpath)
W: no module named win32api (delayed import by iu)
W: delayed __import__ hack detected at line 0 - encodings (C:\Python23\lib\encodings\__init__.pyc)
W: delayed conditional __import__ hack detected at line 0 - encodings (C:\Python23\lib\encodings\__init__.pyc)
W: __all__ is built strangely at line 0 - re (C:\Python23\lib\re.pyc)
W: __all__ is built strangely at line 0 - dis (C:\Python23\lib\dis.pyc)
W: delayed eval hack detected at line 0 - os (C:\Python23\lib\os.pyc)
W: __all__ is built strangely at line 0 - tokenize (C:\Python23\lib\tokenize.pyc)
W: delayed conditional exec statment detected at line 0 - iu (C:\Tools\pyinstaller\iu.pyc)
W: delayed conditional exec statment detected at line 0 - iu (C:\Tools\pyinstaller\iu.pyc)
The batch file I am using to drive this consists of the following two lines:
Makespec.py --debug --onefile --out Test --name QtApp TestSrc\application.py
Build.py Test\QtApp.spec
------------------------------
Gary H. Merrill, Principal Scientist
Analysis Applications, Research, and Technologies
GlaxoSmithKline Research and Development
Research Triangle Park, NC
919.483.8456
| "Giovanni Bajo"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 31-Oct-2005 17:30
|
|
[EMAIL PROTECTED] wrote:
>> I would like to use Pyinstaller for PyQt applications we are
>> developing. Initial experiments have been unsuccessful (I suspect
>> hidden import problems that I have not yet investigated).
>>
>> Is there a simple set of directions for using Pyinstaller for a PyQt
>> application? At the moment I do not care whether the result is a
>> single executable or an executable together with some DLLs. I'd
>> just like, as an initial step, to get one of the PyQt examples to
>> work with Pyinstaller (and Inno Setup -- but the Pyinstaller step
>> comes first).
If you are running PyInstaller 1.0, it should be working with PyQt out of the
box. I routinely package relatively complex PyQt applications with PyInstaller.
One way to debug the problem is to build with debug support (run Makespec
with --debug --console, or modify your .spec file putting debug=1 and console=1
in the right place). With this stuff on, you should be able to see the actual
traceback for the ImportError. If you can report it here, we can see what it is
going on.
Giovanni Bajo
_______________________________________________
PyInstaller mailing list
[email protected]
http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
_______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
