[Mono-list] Installing multiiple Versions of mono, typo corrections
Wed, 10 Nov 2004 16:19:28 -0600
I currently have the same setup with you on my Mac, what i did was
setup my .bash_profile with something like this:
test -r ~/.monolatest && source ~/.setmonolatest
~/.monolatest is nothing but an empty file which i can touch(touch) or
remove(rm) depending on which environment i like to work with.
and in my ~/.setmonolatest, i place the path of my monolatest and all
other necessary env vars
I not know English well, but I know 7 computer languages.
On Nov 10, 2004, at 6:23 AM, Philipp Knecht wrote:
> Thanks Jon
> That cleared things up. Didn't know that there exists
> a GAC in mono. Is mono using strongnamed assemblies?
> One more question (remember i'm a newbie and learning
> linux on my own)
> Where can i set those enviroment variables (defaults)?
> - .bashrc
> - or profile.bashrc
> - or rc.2,rc.3,... (runlevel scripts)
> - or init.d
> - somewhere else
> I'm using putty with winxp to handle the
> ubuntu-console so i don't wanna use any "click click
> hooray!" stuff ;-)
> i'm still a bit groggy with console commands but feel
> this is the way to go.
> --- Jonathan Pryor <email@example.com> schrieb:
>> On Wed, 2004-11-10 at 05:25, Philipp Knecht wrote:
>>> I wanna use 1.0.4 (stable) and latest on the same
>>> I use Ubuntu 4.10. I've already compiled and
>>> 1.0.4 (libgdiplus,mono,mcs,xsp,gtk# in this
>>> order) with the prefix /usr/local.
>>> Now i'll download the latest tarball and
>>> compile/install it too. Are there any pitfalls
>> when i
>>> use ./configure --prefix=/usr/local/monolatest?
>>> Are there any enviroment variables to set? if yes
>> Of course there are pitfalls. There's always
>> pitfalls. :-)
>> The primary pitfall is maintaining your sanity.
>> Since you have to
>> modify environment variables to switch between the
>> two versions of mono,
>> your entire build environment then depends on the
>> variables. Change environments, and things change
>> -- for example, CVS
>> mono won't build from Mono 1.0.4 (sorta), so if Mono
>> 1.0.4 is found in
>> your path, you get lots of build errors about how
>> the runtime versions
>> Once you stay consistent with the environments, you
>> only need to worry
>> about the environment variables. You'll need to
>> export PATH=$MONO_PREFIX/bin:$PATH
>> I do the same thing with my own build environment,
>> and things
>> work...when I remember to use the right environment.
>> You may also need to set MONO_GAC_PREFIX, so that
>> when you're using
>> "monolatest" you can continue to use the Mono
>> 1.0.4-installed assemblies
>> (such as Gtk# 1.0.x when monolatest has Gtk# 1.9.x).
>> MONO_GAC_PREFIX to the prefix directory of your Mono
>> 1.0.4 install:
>> export MONO_GAC_PREFIX=/usr
>> # or whatever the prefix of your 1.0.4 install is
>> - Jon
>> Mono-list maillist - Monofirstname.lastname@example.org
> Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier
> anmelden: http://mail.yahoo.de
> Mono-list maillist - Monoemail@example.com