MSYS, Linux, Unix & Mac OS
Under unix/Linux/MSYS, Vish is started via the binary that is located in the bin/arch-XXXX folder of the Vish directory where XXXX is the respectively selected architecture, i.e. platform and compilation options. Vish is started by giving the full path to this folder such as
, provided Vish has been installed in the home directory of a user named “myself” in a subfolder called vish.
For convenience, one may either define an allias in the unix shell
such that typing “v” can be used as a shortcut for the complete path, or one can expand the environment variable PATH to include the Vish bin directory:
The second variant also allows to invoke other utilities that come with Vish, such as F5ls.
Note for Unix-Novices: Both commands need to be typed each time a new terminal or shell is opened. For convenience, they can also be added in the ~/.bashrc file which is read any time a new shell is started.
Recommendation: The vish bashrc setup
For convenience, there is a bash-script in vish’s bin/bashrc that can be included in ~/.bashrc, it will set the aforementioned alias and also provide a couple of other aliases and functions. Just place
export MAKE_CFG=OptDeb . ~/vish/bin/bashrc SetVishExecutablePath
in your local ~/.bashrc shell startup script to activate it. It will print an initial message and set the shell prompt to some special value with more colors and information. Then use “v” to just start the vish that has been selected with the MAKE_CFG compilation option. Use “vo” to start the optimized version, compile using “mm” to start mingw32-make under MSYS or the normal make under Linux/Unix. Via “mo” it will compile in optimized mode, overriding the MAKE_CFG compilation variable for a specific compilation.
Under Windows is it sufficient to call the binary vish.exe from vish/bin/$arch/ where $arch stands for some description of the current platform, for instance arch-i686-w64-mingw32-Debug , which is evident out of the context in the current application.