On Thursday 06 of March 2014 10:47:57 Kene Meniru wrote: > Hi, Thanks. > > So far am able to do 'pyinstaller --name program program.py' and it > magically pulls all the parts of the program into one directory nicely. My > problem is the GUI part. You see the GUI module is standalone. It provides > the user with menu's and a text dialog to create a script file. The first > line in the script file imports program.py and when the user has finished > creating the script file clicks a button and the GUI system basically calls > python to process the file. So there is no connection between the > program-GUI.py and program.py via an import. > > I hope that makes sense.
It looks like you might need to call pyinstaller twice - to create two
executables or use the 'multipackage' feature of pyinstaller.
- Program
- README
- program/
- __init__.py
- program.py
- programApp.py
- programData.py
- programModule1/
- __init__.py
- programModule2/
- __init__.py
- bin/
- program_GUI.py
Based on your structure you would call pyinstaller twice (not considering
multipackage feature):
cd Program/
pyinstaller program/program.py
pyinstaller --paths=. bin/program_GUI.py
dot '.' is reference to your current working directory or you could use
absolute path C:\any\absolute_path\Program\
With the --paths option you tell pyinstaller where to look for additional
python modules - in your case you need to include location of modules that are
used by the program.py
signature.asc
Description: This is a digitally signed message part.
