Hello,
Can you test Monobjc 4.0.436 + Mono 2.6 RC together ?
Regards, Laurent Etiemble.
2009/12/13 Duane Wandless :
> An update on the Mono 2.6 RC. As expected the thread_get_state crash still
> exists with Monobjc 2.0.413.0. I have not tried with 2.0.436.0.
>
> I do have the MD soft debugger
An update on the Mono 2.6 RC. As expected the thread_get_state crash still
exists with Monobjc 2.0.413.0. I have not tried with 2.0.436.0.
I do have the MD soft debugger working with my embedded monobjc app. It is
not perfect as sometimes the app freezes but this could be a cause of the
thread
Laurent,
> I understand your point and also think that providing a custom runtime
> can be awkward. I am still working hard to have a clean an acceptable
> solution to the problem.
>
> The Monobjc 4.0.436 (dylib inside) has solved some crash problems but
> not all. That makes me say that there ar
Hello,
I understand your point and also think that providing a custom runtime
can be awkward. I am still working hard to have a clean an acceptable
solution to the problem.
The Monobjc 4.0.436 (dylib inside) has solved some crash problems but
not all. That makes me say that there are other cases
The way I see it, even asking users to install the regular Mono on OS
X is too much. Especially because things tend to break with newer/
multiple versions of Mono on Mac.
This solution is perfect for deployment, because we deploy after using
mkbundle (= package this mono version in the app).
Am i the only one who thinks this custom runtime thing is not really acceptable
for anyone who wants to - oh, say - *deploy* applications to regular users who
can't/won't just patch their Mono install? what's the short-term plan for
enabling people to actually ship apps based on Monobjc, and why
A quick update. I've only tested Snow Leopard with *success*. I have not
seen the thread crashing issue. Using 2.4.2.3_M and 2.0.413.0. SL 10.6.2.
I'm hoping to test Leopard later today or tomorrow.
The UI is native Cocoa calling into an embedded mono runtime. The C# code
is multithreaded han
Hello,
Sorry for the late update, but I had some busy nights trying to find
another work-around for the Snow Leopard crash. The 4.0.436 release of
the Monobjc bridge has brought mixed results regarding the Snow
Leopard crash: some users have reported success while others have
reported nasty crashe
Laurent,
> Have you copied the two native libraries in the MacOS folder of the bundle ?
> Note that the bootstrap script has been changed to include the MacOS folder
> into the LD_LIBRARY_PATH, so you have to also check it.
i didn't the first part, yes. i'll have a look at the updated bootstrap
Hello,
Have you copied the two native libraries in the MacOS folder of the bundle ?
Note that the bootstrap script has been changed to include the MacOS folder
into the LD_LIBRARY_PATH, so you have to also check it.
Regards, Laurent Etiemble.
2009/11/22 marc hoffman
> Laurent,
>
> im getting t
I ran into this issue as well. In my opinion this is a limitation of Mono.
Mono should look in the path of the running EXE or DLL. To truly embed mono
in an application this would be ideal.
http://www.mono-project.com/Interop_with_Native_Libraries
Basically you have setup an env variable or pla
Laurent,
im getting the following error, although the dylib(s) *are* deployed in the
MacOS folder of the .app bundle. Snow Leopard 10.6.2, using the current stable
2.4.2.3_6 version of Mono.
11/22/09 3:14:57 PM [0x0-0x5df5df].DAServer6[29474] Unhandled Exception:
Monobjc.ObjectiveCExceptio
ative bundle. I have some custom code to add
> dllmap
>> entries into the configuration, so manually added an entry for
>> libmonobjc.2.dylib.
>>
>> Incredible thank you for crafting this fix. It's really nice that there's
>> not need to make changes to the mono runt
,
> Anthony
>
> -Original Message-
> From: Anthony Bowker [mailto:anth...@flowol.com]
> Sent: Wednesday, November 11, 2009 10:37 AM
> To: users@lists.monobjc.net
> Subject: RE: [us...@lists.monobjc.net] Snow Leopard support: call for
> testing
>
> Thi
...@lists.monobjc.net] Snow Leopard support: call for testing
Hello,
I have finally come to a solution regarding the Snow Leopard support:
I have introduced a native library into the bridge to avoid the
reported crash on Mac OS X 10.6 [1]. After reviewing all the
feebacks[2][3], I came to the conclusion
Hello,
I have finally come to a solution regarding the Snow Leopard support:
I have introduced a native library into the bridge to avoid the
reported crash on Mac OS X 10.6 [1]. After reviewing all the
feebacks[2][3], I came to the conclusion that a native library was the
only solution to:
- avoid
16 matches
Mail list logo
