To build Virtaal yourself, you will need a packaged archive of the Virtaal source code, or obtain it directly from Git.
To get the source code direction from Git use this command:
git clone email@example.com:translate/virtaal.git
These are not build dependencies but usually improve the user experience.
You should be able to run Virtaal from the source tree. If you would like to install Virtaal, you can build it using
and then you can install it with
sudo ./setup.py install
For users running from a tarball, we do some dependency checking when starting Virtaal to be able to give accurate error messages in case of missing dependencies. However, if you have all of these sorted out in your package dependencies, there is no need for Virtaal to do this any more. In the file bin/virtaal, uncomment the line
#packaged = True
by removing the hash sign. This way Virtaal can start a bit quicker with no loss of functionality.
For the translate-toolkit, be sure to get the Python library – the one marked win32.exe – and not the stand-alone Windows installer, which is labelled setup.exe. You might need to create this yourself with
python setup.py bdist_wininst
or just ensure that the Translate Toolkit is in your PYTHONPATH.
If you would like to build a stand-alone Windows installer, you will also need to get:
This is just some notes – it is incomplete and might be entirely off the mark. Virtaal and all dependencies run on OSX, but we still need help to document the simplest process, and to build installable packages.
This was tried so far on Mac OSX Tiger (10.5):
Install the “inst” directory from this disk image somewhere: http://www.immunityinc.com/downloads/CANVAS_OSX_SUPPORT.dmg
This GTK+ port does not need X11.
add inst/lib/python2.5/site-packages to PYTHONPATH
run python bin/virtaal
If you want, get the OS X Leopard theme: http://kims-area.com/?q=node/4 Install it into inst/share/themes/ and add an environment variable:
export GTK2_RC_FILES=inst/share/themes/OS\ X\ Leopard/gtk-2.0/gtkrc