This section assumes GNOME is installed in /opt/gnome.Ĭreate a bash script named something like ~/mono-dev-env. To prevent introducing elements from the existing Mono environment, a new environment must be set up. autogen.sh script to generate the autotools build system before you will be able to run. If you are using Git rather than released tarballs, you must run the. Respective modules are: mono, libgdiplus, and gtk-sharp. Modules in Mono Git correspond to the source tarballs above.
This document is concerned only with mono, libgdiplus, gtk-sharp-1.x, gtk-sharp-2.x, and mono-tools. Source Tarballsįirst, download the Released Source Mono Tarballs. The “parallel” environment this document details is installed from either source tarballs or from Mono Git repository. This document assumes that a distribution-installed Mono environment already exists, and is installed in a prefix other than /opt/mono.
It is possible to run the latest versions of these applications (for example, from Mono Git) with the latest version of Mono by installing all components into a separate prefix with different environment variables. It may be desirable to have two or more completely separate and independent Mono stacks running at the same time, for development purposes or even for running unstable applications without compromising existing installed stable versions.įor example, under SUSE 10 Mono, Banshee, F-Spot, and Tomboy (to name a few) are all installed by default, are considered “stable,” and are linked against “stable” Mono libraries, such as gtk-sharp-2.x.
This assumes that you are familiar with the compilation process for Mono.
#PARALLELS INSTRUCTIONS FOR MAC HOW TO#
This document details how to run multiple Mono environments on a single system where neither environment conflicts with another.
0 kommentar(er)
