COMPILING VISH UNDER WINDOWS 7 A� (status as of Apr. 2016)

Initial Steps

  1. Tortoise SVN (optional)
  2. Msys
  3. Checking out VISH
  4. After Checkout
  5. Starting Vish

VISH depends on successful QT installation for it to compile. The QT version is the determining factor on which gcc compiler to use which will determine what MSYS and MinGW version to use.

To install Vish for compilation from source, the following steps are required:

1.Tortoise SVNA�

Tortoise SVN is a free software that can optionally be used and is recommended for easy accessing the source code of Vish via SVN, just by right clicking on your destination folder, when in the windows explorer.

2.MSYS

Is to be installed with the minGW-installer (mingw-get.exe)
Once installed, there should be a new icon on your deskop called a�?MSYSa�?. If this is not the case, the MSYS/MinGW prompt should be findable through the windows start menu or via a search in the explorer.

The installation of the following MinGW packages will be required:

a.) MSYS Basic System

b.) at least one of the console tools:

  • msys-rxvt
  • msys-console
  • msys-minttyA�(Note: open minGW-installer and search in “all packages.”. A� Look in “C:\MinGW\msys\1.0\bin” for A�”mintty.exe”. A�Start it and with a mouse click. Right click in the task bar on the mintty icon and pin it. Then with a right click on your mintty terminal a small window pops up and there you chose “Terminal” and do a right click. A� Then you click on properties. A�In the command line specified in the target input field add a minus like this: “C:\MinGW\msys\1.0\bin\mintty.exe -” A�)

You can install all and choose later the most convenient.

c.) msys-bison (optional but good to have, compiler compiler)

Make sure to uncheck (not installing) the following packages:

  • msys-make
  • mingw32-gcc

Download link: https://sourceforge.net/projects/mingw/files/Installer

d.) Install qt5 (64 bit recommended) (https://sourceforge.net/projects/qt64ng/). Extract the file into the default folder as suggested by the installer. Note: any other name than qt5 is ok but avoid special character such as spaces, parenthesisA�, semi colon etc. .

It is necessary to set the PATH such that gcc and moc can be found.

To do so go into your user-folder (e.g. ~/minGW/msys/1.0/home/USERNAME) and create a new file usingany convenient editor(eg. Notepad++), insert

export PATH=/c/Qt/qt-5.5.0-x64-mingw510r0-seh-rev0/mingw64/bin:/c/Qt/qt-5.5.0-x64-mingw510r0-seh-rev0/qt-5.5.0-x64-mingw510r0-seh-rev0/bin:$PATH

(resp. Pathname of your QT-directory/bin)a�? and save it as: a��a��.profilea��a��

( Note: no other extensions to the file. In your explorer it should appear as .profileA� And look out for / vs.\A� doing copy paste !)

Check for the correct path by using the which command in bash for gcc and moc, it should look like this:

~$ which gcc
/c/Qt/qt-5.5.0-x64-mingw510r0-seh-rev0/mingw64/bin/gcc
~ $ which moc
/c/Qt/qt-5.5.0-x64-mingw510r0-seh-rev0/qt-5.5.0-x64-mingw510r0-seh-rev0/bin/moc

3. A�Checking out VISHA�

Once youa��re an Assembla project member, you can checkout the VISH sources from the repository usingSVN software.

It is recommended to install VISH into a directory in your MSYS Home folder, for instance C:\msys\1.0\home\USERNAME where USERNAME is your windows user name.

!!!!Make sure no [space] is used in the USERNAME, as this will very likely cause conflicts !!!!

There are two ways to run the SVN checkout.

A) Using TortoiseSVN free software (recommended for

A� A� A� A� A� A� inexperienced user):

Once Tortoise SVN was successfully installed (it recommends to reboot after installation, however it is sufficient to just restart the windows explorer), then right-click on the folder mentioned above to get to the SVN Checkout menu and enter the Vish SVN URL

(checkout URL: https://subversion.assembla.com/svn/vish/trunk).

Select a�?visha�? as the checkout directory (default might be a�?trunka�?) and enter your Vish SVN credentials for the assembla.com server.

B) Using the shell for checkout:

Move to your destination directory and type:

svn co https://subversion.assembla.com/svn/vish/trunk vish

4. A�After Checkout

a. Get your Msys & console runnig:

To invoke the rxvt-console browse and run

msys.bat. The *.bat should be in location ~/msys/1.0/win/msys.bat. If not, use the search function on your msys folder.

When the app. is running, pin the application to your task bar. Then rigthclick twice (first on the app icon on the bar, second on the small tab that opens).

Choose a�zPropertiesa�? and change the applicationa��s target to ~/msys/1.0/msys.bat a��rvxt[means: a�zminus minusrvxta�?]

The *.exe for the Console should be situated in

~/msys/1.0/lib/console2. If you can not find the *.exe,A� see Troubbleshooting section. When activated, pin it to your taskbar for quick access.

The same steps are required for the mintty-console, which path should be ~/msys/1.0/bin/mintty.exe -A�

[means: a�zmintty.exesSPACEminusa�?]

You should now have a window with a command prompt (shell). From this point on the same instructions are valid like under linux/unix:

b.After your shell has started you can see directories using a�?lsa�? or a�?ls-la�? and use a�?cda�? or a�zcd ..a�? to move through directories into ~vish.

c.When reaching the location ~vish using above commands run a�?minGW32makea�? command in this directory to start the compilation process

minGW32-make
This will take a while. Watch for errors, in particular about a�?QT not founda�? (see Troubleshooting section). Vish will be successfully installed, when Compilation has been finished successfully and you see the fish:

A�Schnappschuss (2014-08-19 11.19.26)

Optionally do a�?minGW32-make -j4a�? to enable parallel compilation (the number a�?4a�? stands for the available processors to use, higher numbers are suitable for multicore machines). This is faster (approx. 20minutes on a decent workstation), but unreliable, and might possibly stop with a (non-serious) compilation error. If so, just repeat typing a�?minGW32-make -j4a�?.

Sometimes parallel compilation produces corrupted files, probably a bug in GNU Make in combination with certain file systems. In that case, the file will be indicated in an error message like a�?Error: File.o truncateda�? and needs to be removed manually.

In any case, compilation was successful if the fish (as shown above) is displayed on the screen.

5. A�Starting Vish

To invoke Vish from the command line, give its absolute path: ~/vish/bin/arch-x86_64-Debug/vish.exe
It is convenient to set an alias in the MSYS shell for this purpose. So edit your .profile such as in
alias v=~/vish/bin/arch-x86_64-Debug/vish.exe
which allows to invoke vish from the bash by just typing a�sva��.

For more alias proposals and other tips see Convenience Hints

Please let us know about any problems occurring during this installation process.

top