What is our intent with adding all these registry keys?
It seems as if they are helpful for installing mono,
but might get in the way of installing MS .net.
If that's the intent, do y'all want me to make the
dotnet20 winetricks verb remove any registry
keys that confuse the dotnet20 installer?
Dan Kegel d...@kegel.com writes:
What is our intent with adding all these registry keys?
It seems as if they are helpful for installing mono,
but might get in the way of installing MS .net.
If they prevent installing MS .NET there should be a way to undo them
like we do for IE, by
On Tue, Aug 24, 2010 at 1:52 PM, Alexandre Julliard julli...@winehq.org wrote:
What is our intent with adding all these registry keys?
It seems as if they are helpful for installing mono,
but might get in the way of installing MS .net.
If they prevent installing MS .NET there should be a way
Dan Kegel dank at kegel.com writes:
What is our intent with adding all these registry keys?
It seems as if they are helpful for installing mono,
but might get in the way of installing MS .net.
If that's the intent, do y'all want me to make the
dotnet20 winetricks verb remove any registry
And eventually mono will be installed automatically like gecko is?
If I ever get the damn thing to build fully on a Linux box, yes.
Yes, build-mingw32.sh works, but the resulting build is incomplete.
For example, it lacks libgluezilla and a mozilla library to glue to,
so the browsing component does not work. This is in the official
Windows builds of Mono.
I don't know what else is missing.
On Tue, Aug 24, 2010 at 12:45 PM,
--- On Tue, 24/8/10, Vincent Povirk madewokh...@gmail.com wrote:
And eventually mono will be
installed automatically like gecko is?
If I ever get the damn thing to build fully on a Linux box,
yes.
Is there a problem with that? Mono comes with a script called
build-mingw32.sh for
