[tor-bugs] #7283 [Flashproxy]: flashproxy-client Windows .exe packages

[Tor Bug Tracker & Wiki]

#7283: flashproxy-client Windows .exe packages
------------------------+---------------------------------------------------
 Reporter:  dcf         |          Owner:  aallai        
     Type:  task        |         Status:  needs_revision
 Priority:  normal      |      Milestone:                
Component:  Flashproxy  |        Version:                
 Keywords:              |         Parent:  #7166         
   Points:              |   Actualpoints:                
------------------------+---------------------------------------------------
Changes (by dcf):

  * status:  new => needs_revision


Comment:

 aallai made a branch implementing this at
 https://github.com/aallai/flashproxy/tree/make_exe.

 I made a branch too at https://git.torproject.org/user/dcf/flashproxy.git
 branch `make_exe`; please pull from it.

 Here are notes on the changes:
  * Please see if there is a way to build all the executables with one
 invocation of PyInstaller. To do this, you might have to create your own
 spec file with multiple calls to `Analysis`. Here are some example links:
    * http://www.pyinstaller.org/export/develop/project/doc/Manual.html
 #spec-files (look at `MERGE`)
    * http://stackoverflow.com/questions/8888813/packaging-multiple-
 scripts-in-pyinstaller
  * I want to keep the `.exe` extensions on files. Running the registration
 helpers with `--register` worked just fine for me with the `.exe`
 extensions, with no code changes.
  * See if there is a way to cause PyInstaller to put its scratch files in
 a subdirectory. As it is, it implicitly uses the name `dist` in the
 current directory, which conflicts with our use of the same name.
  * After PyInstaller, there shouldn't be any leftover build files or
 autogenerated spec cruft. `git status` should be clean. A nice way to do
 this might be to make the intermediate files
 [https://www.gnu.org/software/make/manual/html_node/Chained-Rules.html
 #Chained-Rules .INTERMEDIATE] in the makefile; another way is to
 explicitly delete them.
  * Is it possible to make the build fail if m2crypto is missing? I tried
 building an exe before installing it, and the build worked, though of
 course `flashproxy-reg-email` didn't work.

 What I would ideally want is a `dist-exe` target that builds `flashproxy-
 client-VERSION-win32.zip`, which contains the same files as `flashproxy-
 client-VERSION.zip`, except that the Python script files are replaced by
 `.exe`s. All the auxiliary PyInstaller files are ideally in a subdirectory
 within the zip.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7283#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online