Changes between Initial Version and Version 1 of Ticket #1093, comment 6


Ignore:
Timestamp:
2010-06-27T23:46:02Z (14 years ago)
Author:
zeromus
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1093, comment 6

    initial v1  
    1 It seems that the tahoe.exe included with Allmydata321Setup.exe behaves similarly to the tahoe 1.7.0 py2exe builds I was making. "tahoe start" yields "Can't find twistd (it comes with Twisted).  Aborting." while "tahoe run" just exits immediately. It turns out, this is because "tahoe run .\node" doesn't work. There are some docs or bugs somewhere that advise that "tahoe run ." doesn't work in windows--I thought that was strange, but did not expect it to apply to any relative path. Changing the command to "tahoe run c:\path\to\node" causes "tahoe run" to work as expected.
     1It seems that the tahoe.exe included with Allmydata321Setup.exe behaves similarly to the tahoe 1.7.0 py2exe builds I was making. "tahoe start" yields "Can't find twistd (it comes with Twisted).  Aborting." while "tahoe run" just exits immediately. It turns out, this is because "tahoe run .\node" doesn't work. There are some docs or bugs somewhere that advise that "tahoe run ." doesn't work in windows--I thought that was strange, but did not expect it to apply to any relative path. Changing the command to "tahoe run -C c:\path\to\node" causes "tahoe run" to work as expected.
    22
    33Bug still remains: can't py2exe a tahoe build made with either python25 or python26. Am going to try bbfreeze when i get a chance.