#425 closed task (wontfix)

set up buildslave for Windows SMB (WinFUSE) frontend

Reported by: warner Owned by: ndurner
Priority: major Milestone: eventually
Component: packaging Version: 1.0.0
Keywords: windows test docs smb install buildbot Cc:
Launchpad Bug:

Description

We'd like to get the source code for our winfuse plugin (plus the installer that allmydata.com makes available on the [http://allmydata.com/download download page]) into the open. The long-term plan is to have a buildbot that will compile/build this installer automatically upon each checkin, just like we do for debian packages and the Mac application.

The first step towards this goal will be to document the build process: a recipe that starts with "svn checkout ...", then has some instructions like "push the 'Build All' button in this IDE", and ends with "copy the .../foo.exe up to the web server".

Mike, could you make up such a recipe and attach it to this ticket? That will help us make progress on the automation task.

Change History (17)

comment:1 Changed at 2008-06-04T20:44:04Z by booker

  • Resolution set to fixed
  • Status changed from new to closed

Building the windows components requires a Visual Studio 2005 compiler. The batch file currently expects this to be installed in the standard install location "C:\Program Files\Microsoft Visual Studio 8"

To build the windows components use the following steps:

  1. checkout the latest source using darcs from user@…:/home/darcs/tahoe-w32-client
  1. execute the winbuild.bat file located in the "./tahoe-w32-client/WinFUSE" directory
  1. Copy the following list of files from the "./tahoe-w32-client/WinFUSE/bin/Release" folder into the installation directory.

WinFUSE.exe.config WinFUSE.exe TahoeFS.dll NeoGeo?.Library.SMB.Provider.dll NeoGeo?.Library.SMB.dll AllmydataTray?.exe AllmydataMapping?.exe AllmydataManager?.exe allmydata_requires_permission.exe

  1. After installation the above list of files should end up in the "C:\Program Files\Allmydata 3.0\Install\winfuse" directory.

comment:2 Changed at 2008-06-04T20:44:30Z by booker

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:3 Changed at 2008-06-04T21:09:57Z by booker

Second update to build process just to fix formatting.

  1. checkout the latest source using darcs from "dev.allmydata.com:/home/darcs/tahoe-w32-client"
  1. execute the winbuild.bat file located in the "./tahoe-w32-client/WinFUSE" directory
  1. Copy the following list of files from the "./tahoe-w32-client/WinFUSE/bin/Release" folder into the installation directory.

WinFUSE.exe.config
WinFUSE.exe
TahoeFS.dll
NeoGeo.Library.SMB.Provider.dll
NeoGeo.Library.SMB.dll
AllmydataTray.exe
AllmydataMapping.exe
AllmydataManager.exe
allmydata_requires_permission.exe

  1. After installation the above list of files should end up in the "C:\Program Files\Allmydata 3.0\Install\winfuse" directory.

comment:4 Changed at 2008-06-10T17:14:34Z by warner

  • Owner changed from booker to somebody
  • Status changed from reopened to new
  • Summary changed from document winfuse build process to set up windows-fuse buildslave

awesome, thanks!

comment:5 Changed at 2009-06-21T19:33:32Z by zooko

  • Keywords fuse test added

comment:6 Changed at 2009-06-21T19:34:16Z by zooko

  • Keywords fuse removed

comment:7 Changed at 2009-06-30T12:40:12Z by zooko

  • Owner changed from somebody to ndurner

Hm, I think this ticket is mostly done -- http://allmydata.org/trac/tahoe-w32-client . Is anything missing? I'll ask Nils Durner. ndurner: would you say that the Windows client is fully visible to the public now? Thanks.

comment:8 Changed at 2009-06-30T18:11:22Z by zooko

  • Milestone changed from 1.5.0 to eventually

comment:9 Changed at 2009-12-12T02:45:18Z by davidsarah

  • Keywords indows docs winfuse added; win32 removed

comment:10 Changed at 2009-12-12T02:45:30Z by davidsarah

  • Keywords windows added; indows removed

comment:11 Changed at 2009-12-12T02:46:24Z by davidsarah

  • Keywords install added

comment:12 Changed at 2010-01-09T20:51:48Z by davidsarah

  • Keywords buildbot added

Related to #340?

comment:13 Changed at 2010-02-11T00:37:48Z by davidsarah

  • Keywords smb added; winfuse removed
  • Summary changed from set up windows-fuse buildslave to set up buildslave for Windows SMB (WinFUSE) frontend

comment:14 follow-up: Changed at 2011-01-02T22:25:59Z by francois

Hmmm, shouldn't this ticket also be closed because of the removal of the Windows application in #1282?

comment:15 in reply to: ↑ 14 Changed at 2011-01-03T02:36:47Z by davidsarah

Replying to francois:

Hmmm, shouldn't this ticket also be closed because of the removal of the Windows application in #1282?

Have we given up on getting the NeoGeo SMB library open-sourced? If we have, then we might as well wontfix all of the WinFUSE tickets (which happens to be only this one and #376).

comment:16 follow-up: Changed at 2011-01-03T06:22:20Z by zooko

Yes, I give up on getting the source code to the NeoGeo SMB library. However, people should investigate dokan! :-)

Last edited at 2011-01-03T06:22:38Z by zooko (previous) (diff)

comment:17 in reply to: ↑ 16 Changed at 2011-01-03T07:31:04Z by davidsarah

  • Resolution set to wontfix
  • Status changed from new to closed

Replying to zooko:

However, people should investigate dokan! :-)

The development of that seems to have picked up a bit since the last time I looked. Also there is a 'Dokan SSHFS', which is certainly worth testing with the SFTP frontend (#1289).

Note: See TracTickets for help on using tickets.