##tODE Windows Client Installation
-
Download and install GitHub for Windows by following the instructions on the GitHub for Windows page.
-
Using the GitHub for Windows interface, clone your fork of the gsDevKitHome project project.
-
In GitHub for Windows, go to the Options page and set your default shell to Git Bash.
-
Use the Open in Git Shell menu item in the
gsDevKitHomerepository to open a bash shell and define the$GS_HOMEenvironment variable and add$GS_HOME/binto your$PATH:cd gsDevKitHome export GS_HOME=`pwd` export PATH=$GS_HOME/bin/windows:$PATH
-
Using the bash shell, clone the tode and ston projects to the root of your C: drive. We're manually cloning
tODEto avoid hitting the 256 character path limit for Windows and rooting the repository at the C: keeps the longest paths in tODE out of trouble. Thestonproject needs to be cloned, because the version of Metacello ppresent in the standard Pharo3.0 image, cannot download projects directly from GitHub:cd /c git clone https://github.com/dalehenrich/tode.git cd tode git checkout master cd /c git clone https://github.com/dalehenrich/ston.git cd ston git checkout pharo
-
Checkout your branch of the gsDevKitHome project:
cd $GS_HOME git checkout -b <your branch name>
-
Install GemStone/S (for GCI library files) and Pharo, build the tODE client image and launch the tODE client. The GemStone version that specify in the following should match the version installed on your server machine:
installWindowsClient 3.2.3 c:/tode c:/ston
-
Once the tODE client image comes up, you need to edit the session description for your stones using the
tODE editmenu:Replace the name of the netldi with the port number of the netldi obtained from the stones command (run on the server):
-
Commit the changes that you've made and push them to GitHub, so that you can share the changes with your installation on the server machine:
git status # see what changes have been made git add --all # stage the changed files git commit -m"use port number of netldi" # commit changes git push origin <your branch name> # push the changes to GitHub
Here's the list of scripts that can be used on the client machine.

