[Mono-osx] Mono 2.8.2 and 2.10 regressions

dgdw david.drysdale-wilson at linn.co.uk
Sun Feb 20 12:58:48 EST 2011

Miguel de Icaza wrote:
>> Issue 1: WinForms Form.OpenDialog() causes a segmentation fault
>> I think this issue first appeared in 2.8 and it is certainly present in
>> 2.8.2. I have not managed to check to see if this issue has been resolved
>> in
>> 2.10.
> Please test on Mono 2.10 and file a bug report.

Form.OpenDialog() works as expect in 2.10.

Miguel de Icaza wrote:
>> Issue 3: Packaging mono with an application for distribution.
>> I first tried this with 2.6.4 and I got it to work eventually but had
>> issues
>> with getting the WinForms stuff to work. I have since stripped out all
>> the
>> WinForms stuff from my application and tried it again with 2.8.2 it now
>> just
>> segmentation faults when running the application.
> We never really supported shipping Mono with an app back in the 2.6.x
> days, if you managed to get it working, it was likely pure chance.

Just so I am clear we are talking about the same thing here I am trying to
use mkbundle to create a package that has all the files a user would need to
run my application without installing mono. I had a post about this when I
was trying it with 2.6.4
Are you saying that 2.6.4 never supported the mkbundle tool? Do 2.8.2 and
2.10 support the mkbundle tool?

Miguel de Icaza wrote:
> When people bundle Mono with their apps sometimes they forget to ship
> all the files that Mono needs.  Perhaps you are missing the .config
> file that maps libraries, and perhaps you are missing initializing the
> Mono runtime to look for its libraries in the package-relative
> directory instead of the system files.
> You will have to debug this on your own, try attaching with GDB and
> finding out what happened.

Does the mkbundle tool not handle including all the assemblies and files
required to ship an application without mono? I am quite new to trying this
process out as most of the applications I have shipped to now have been for
Windows or Linux and the inclusion of mono is either no issue or not much of
an issue, however with Mac it becomes a barrier to people using your
application. From what you have indicated it sounds like the process of
bundling mono with an application is not as simple as just running the
mkbundle command. Is there any documentation that runs through what is
required to ship an app with mono? I have found very little on this subject.


View this message in context: http://mono.1490590.n4.nabble.com/Mono-2-8-2-and-2-10-regressions-tp3314159p3315325.html
Sent from the Mono - OSX mailing list archive at Nabble.com.

More information about the Mono-osx mailing list