[tahoe-dev] Building tahoe-lafs on 64bit Windows 7 - Part 1, The building bits.

[David-Sarah Hopwood]

On 15/01/13 05:46, knuttila @dslextreme.com wrote:
> Step 4 blunts its nose into the wall. The root cause is needing a 64bit twisted -- but the 
> symptom is "Unable to find vcvarsall.bat". "google is your friend" on this sort of thing.
> Some rummaging, and you find there's a couple of ways to make the message go 
> away.
> 
> Current solution -- basically, go to Twisted Matrix _(_http://twistedmatrix.com/trac/) and
> look for
> the current win7 64bit version. I used: "Twisted-12.3.0.win-amd64-py.2.7.msi". 

Unfortunately the precompiled "egg" for that dependency is missing for 64-bit Python 2.7
on Windows:

https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html

which is why it tried to compile from source.

> Aside: it turns out that you can install the 32bit Twisted version as well, and it will make 
> the message go away.

That won't work.

> Step 5 won't work -- at least as far as I can see. The python file named "tahoe" appears to
> need a "c:\Python27\python.exe" in front of it. (I'm a linux guy -- on any unix, we can use
> the shell trick of marking a file executable, and giving the name of the interpreter in the
> first line. What is the equivalent trick for DOS/Win7?) In any event, if you want to actually
> run tahoe, you do something like:
> 
> c:\Python27\python.exe C:\tahoe-lafs\bin\tahoe create-client C:\tahoelafsbase
> 
> Rather than:
> 
> C:\tahoe-lafs\bin\tahoe create-client C:\tahoelafsbase
> 
> as described.

That's odd, it should just work.

- Do you have Python 3.x installed?
- What is the first line of C:\tahoe-lafs\bin\tahoe.pyscript ?
- What version of Python, if any, is first on the PATH? (i.e. what does
  "python -V" report)

> Yes, we did some path tricks, and wrote some cheesy bat files to paper
> over some of this, but it's awkward. (the silly part is I'm sure it's 
> do-able under win7/dos, but I've not run across the formula in casual
> googling)
> 
> The last bit comes from trying to fire it up. I'm missing a bit of notes here, but somewhere
> we got a message moaning about a missing win32 api. I googled that, and came across
> a blog who was following similar footsteps for a different application. Anyway, we installed
> the pywin32 pieces from sourceforge and all that went away.

It shouldn't be necessary to install pywin32. If you uninstall pywin32 (from Add/Remove
Programs), what error message does it give exactly?

-- 
David-Sarah Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 553 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130116/9de182f5/attachment.pgp>