[Mono-winforms-list] Problems with Mac OSX (Intel), Mono 1.1.16.1 and gdiplus

[Susan Mackay]

I think I may have answered my own question - if I have, then is this
situation a "bug"?

I found out about .config files (from a book about developing software under
mono) and I then looked at
/Library/Frameworks/Mono.framework/Versions/1.1.16.1/lib/mono/gac/System.Win
dows.Forms and noticed that under the 1.0.5000.* folder there is a .config
file but not under 2.0.0.* folder. The 1.0.5000 config file contains mapping
instructions to do what I'm after. Therefore I copied the config file into
the 2.0.0 window.

I've noticed that the same situation exists with System.Drawing.

Should the (presumably .NET V2 compatible) 2.0.0 directory contain the
.config files? Should they be the same as the 1.0.5000 version or should
they contain something different?

Cheers,

Susan



(Original message follows...)

Hi,

I've installed the latest Intel package for Mono (1.1.16.1) for the Max OSX
and I'm trying to 'start small' learning Mono (I've come from a Windows
/Visual Studio /C# environment) and I've come across a problem.

My test code is trivial - basically a single call to
System.Windows.Forms.MessageBox.Show(). I complies (gmcs) and runs under
mono until it tries to load the gdiplus.dll library - which it can't find.

I've used the MONO_LOG_LEVEL="debug" and MONO_LOG_MASK="asm,dll" environment
variables, and I can see mono (dlopen actually) trying all sorts of
variations of gdiplus.dll (prefixed with "./" and/or "lib", suffixed with
and without the ".dll" by ".so").

The only gdiplus files on my computer are in
/Library/Frameworks/Mono.framework/Versions/1.1.16.1/lib/libgdiplus.dylib
(and ".a" and ".la" suffixes).

What I don't see is any combination of ".dll" and ".so" suffixes.

Is this a known problem with my configuration?

Is there some way to tell the mono environment to include a check for the
.dylib" suffix?

Thanks

Susan