Not necessarily relevant either, but, to sort of package chunks of files for 
use on windows, I use py2exe, and include data_files to combine in/under /dist 
folder.

Stay well

Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'

  ----- Original Message ----- 
  From: matatk 
  To: [email protected] 
  Cc: [email protected] 
  Sent: Wednesday, June 05, 2013 11:21 PM
  Subject: [AGRIP] Re: Python script for windows


  Note for all readers: this email is about development; when there is an 
official Windows version of the game, none of the steps below will be required; 
it will "just work" as they say (we hope!)


  I've just tried the following to get the python script running on Windows and 
it seems to be working -- though I've not yet complied the engine to test the 
TTS for sure.  I reckon that'll need a bit of work but this is a start...


  1. Get python 2.7 from <http://www.python.org/download/>.
  2. Get pywin for that version of python from 
<http://sourceforge.net/projects/pywin32/files/pywin32/>.
  3. Get the PyGUI package from 
<http://www.cosc.canterbury.ac.nz/greg.ewing/python_gui/> and extract it; move 
the GUI directory to same directory as the script.
  4. Get the pyttsx package from <https://pypi.python.org/pypi/pyttsx> and 
extract it; move the pyttsx directory to same directory as the sript.


  I used 7-zip from <http://www.7-zip.org/> to do the extracting of the .tar.gz 
files.


  There is an error in the PyGUI file win32/ButtonBases.py; as a mailing list 
message I found [1] points out: it should have this line before any other code:
  from GUI.GControls import Control as GControl


  At this point you will be able to run the launcher script on Windows but it 
won't work properly because the game and other files are not in the expected 
places, however this is a good start.  I am now working on compiling the engine 
on Windows.  When that's done I can see about how well the TTS works.


  It would be really helpful to have a build script that puts all the files in 
the right place for the Windows release, much as we have now for OS X (although 
I don't think the script could download things automatically on Windows as I 
don't think there is a built-in command to do that).  I could probably quite 
quickly knock up such a thing in shell scripting language on OS X, which could 
generate a .zip file or similar to send over to Windows and use as the basis 
for building a release, but that would mean that to make a Windows release we'd 
need someone to run a script on UNIX first.  It might be best for me to move 
the files to a less platform-specific place in the repository and then tweak my 
OS X scripts to make the application bundle, and write a batch file on Windows 
to do the same sort of thing on the Windows side.




  Matthew


  [1] <http://mail.python.org/pipermail//pygui/2011-November/000208.html>

  -- 
  You received this message because you are subscribed to the Google Groups 
"AGRIP Project" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
  To post to this group, send an email to [email protected].
  To view this discussion on the web, visit 
https://groups.google.com/d/msgid/agrip-project/bbf43fa3-c2e1-4666-921e-35a1df039207%40googlegroups.com?hl=en-GB.
  For more options, visit https://groups.google.com/groups/opt_out.
   
   

-- 
You received this message because you are subscribed to the Google Groups 
"AGRIP Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send an email to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/agrip-project/6E41BB1621784558B4AAD1B0CDB05858%40jakeslaptop?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to