2

I'm attempting to use Esky to update and freeze a python application. However, part of the application includes static files.

The way Esky appears to behave, is it creates a second .exe outside of the folder which contains all the python libs and static data I'm including.

When I run the exe from the folder itself, everything works fine, but when I run the 'bootstrap' exe esky creates, it can't find the static data (as it's not in the same relative place).

I suppose I could hard code the folder esky creates, but I can't imagine that's the best way to go about it.

Anyone have any helpful tips/tricks/solutions?

Edit: Included folder structure from esky docs

prog.exe                     - esky bootstrapping executable
appdata/                     - container for all the esky magic
  appname-X.Y.platform/      - specific version of the application
    prog.exe                 - executable(s) as produced by freezer module
    library.zip              - pure-python frozen modules
    pythonXY.dll             - python DLL
    esky-files/              - esky control files
      bootstrap/             - files not yet moved into bootstrapping env
      bootstrap-manifest.txt - list of files expected in bootstrap env
      lockfile.txt           - lockfile to block removal of in-use versions
      ...other deps...
  updates/                   - work area for fetching/unpacking updates
moreisee
  • 408
  • 8
  • 17
  • What is `sys.executable` inside your frozen program? Does it change when running from esky's bootstrap? – Thomas K May 14 '13 at 22:16
  • i have static files that esky finds fine when using the boot strapper without doing anything special. – timeyyy Jun 18 '15 at 18:16

0 Answers0