Gonzalo,
Can you please fix Windows threadpool issue first before it becomes
worse than the previous state that we could only revert it to 32b3b31?
Now we cannot even revert it to that revision:
threadpool.c:2025: error: too few arguments to function
`mono_thread_create_internal'
Hi,
I got the thing to work... but I' am not very thrilled with the
resolution... It seems like it'll work only if I use the same string for
both MonoDomain creation thru mono_jit_init and also for loading assembly
thru mono_domain_assembly_open.. In essense I am having to pass the assembly
file
If you saw the example code I sent I was passing the full path to the EXE to
both mono_jit_init and mono_domain_assembly_open.
The purpose of embedding is to embed the Mono runtime into your app so that
it runs without installing Mono. This error indicates the embedded runtime
could not find
Hi
I'm using an i686 machine to cross compile for an arm embedded target, using
arm-iwmmxt-linux-gnueabi toolchain.
I am using the configuration settings below:
CC=/home/ndick/Cross_Library/crosstool/bin/arm-iwmmxt-linux-gnueabi-gcc
./configure --host=arm-iwmmxt-linux-gnueabi
Hi all,
I'm new to .NET and Mono, so some of the terminology in the embedding API isn't
quite clear to me.
What's the difference between a MonoAssembly and a MonoImage?
thanks,
vic
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
Hello Victor,
I'm new to .NET and Mono, so some of the terminology in the embedding API
isn't quite clear to me.
What's the difference between a MonoAssembly and a MonoImage?
Assemblies are the unit of deployment in .NET and the container for
the MonoImage, you will typically see those as
Has anyone written anything like a setup script with something like:
./parallel-mono-install.sh v2.10.1 --path=/opt/mono
and if so, would they be willing to share? I'm finding it obnoxious to
set up unstable Mono versions on new Ubuntu boxes.
http://sadtrombone.com
~ jf
--
John Feminella
Regarding this post on Mono-OSX http://go-mono.com/forums/#nabble-td3251954 and
some of my own issues with Process.Start() on MacOS X.
I've discovered that Process.Start(ProcessStartInfo info) leaves child
processes hanging around until the parent process dies, unless you call
WaitForExit() on
I do not know how you are compiling your OSX app but otool and
install_name_tool were very useful in my understanding of the embedding
process.
If you linking against shared libraries and using install_name_tool,
you'll also want to provide the linker flag -headerpad_max_install_names.
On Mar 15, 2011, at 2:57 PM, Tom Philpot wrote:
I've discovered that Process.Start(ProcessStartInfo info) leaves child
processes hanging around until the parent process dies, unless you call
WaitForExit() on the child process.
...
Is this a bug or by design?
The problem is the
Submitted bug with a reproducible test case:
https://bugzilla.novell.com/show_bug.cgi?id=679936
On 3/15/11 12:26 PM, Jonathan Pryor jonpr...@vt.edu wrote:
On Mar 15, 2011, at 2:57 PM, Tom Philpot wrote:
I've discovered that Process.Start(ProcessStartInfo info) leaves child
processes hanging
Apparently, the bug I filed was marked as a duplicate of this WONTFIX bug:
https://bugzilla.novell.com/show_bug.cgi?id=668867
According to the resolution of that bug, I just need to enable shared
handles. Unless I'm doing something wrong, enabling shared handles should
be as simple as
12 matches
Mail list logo
