Hi again,
It should be now fixed in trunk.
Atsushi Eno
Atsushi Eno wrote:
I'll have a look. However since 4 years have passed since I wrote it,
I'll have to revisit the spec and will take not a little time.
Atsushi Eno
Tom Philpot wrote:
The following program throws an
On Sun, 2009-06-14 at 01:34 +0200, Lucas Meijer wrote:
Hey,
In order to figure out how to properly use the new coreclr
functionality, verifiers etc, I've taken the
test-metadata.c sample that shows how to simply embed mono, and I'm
adding some coreclr stuff to it.
The sample works
On Sun, 2009-06-14 at 01:34 +0200, Lucas Meijer wrote:
Hey,
In order to figure out how to properly use the new coreclr
functionality, verifiers etc, I've taken the
test-metadata.c sample that shows how to simply embed mono, and I'm
adding some coreclr stuff to it.
The sample
On Mon, 2009-06-15 at 15:31 +0200, Lucas Meijer wrote:
On Sun, 2009-06-14 at 01:34 +0200, Lucas Meijer wrote:
Hey,
In order to figure out how to properly use the new coreclr
functionality, verifiers etc, I've taken the
test-metadata.c sample that shows how to simply embed mono,
Hi,
I don't know how Silverlight works on Windows but it should be checked
first.
There are two possible solutions:
1) Load assemblies as byte arrays rather than mapping them using
LoadLibrary when core clr is enabled.
2) Modify the verifier or other code that assumes on-disk layout to be
O.k., thanks to http://shana.worldofcoding.com/en/mono_cygwin_tutorial.html
this tutoial I finally managed to compile Mono.
Now I'd like to compile it for Windows 98. The
http://www.mono-project.com/FAQ:_Technical technical FAQ describes this as
follows:
Can Mono run on Windows 9x, or ME
D.R.W. wrote:
O.k., this description is only semi-helpful.
Firstly, the link to unimono doesn't work at all anymore. Seems like this
FAQ wasn't updated for a long time. Fortunately, libunicows can be found on
the net.
The text in the FAX is addressed to porters and it's likely 5 years
old. No
Recently we added the .Net 4.0 profile to the Mono build. Unfortunately,
at this point, there isn't much there for the majority of users, and it
nearly doubles the build time.
Do we have a make guru who can resurrect our --with-preview=no
configure flag and change it so it turns off the 4.0
Hi,
It would be better to only compile the assemblies in 4.0 which actually
have changes
relative to 3.5.
Zoltan
On Mon, Jun 15, 2009 at 8:20 PM, Jonathan Pobst mon...@jpobst.com wrote:
Recently we added the .Net 4.0 profile to the Mono build. Unfortunately,
at this point,
--enable-net-4-0 --disable-net-4-0 --enable-net-1-1 --disable-net-1-1
etc. would make more sense I think because most likely there will be
more versions and there is no use to call any specific version preview
or legacy.
Jonathan Pobst wrote:
Recently we added the .Net 4.0 profile to the Mono
O.k., this description is only semi-helpful.
Firstly, the link to unimono doesn't work at all anymore. Seems like this
FAQ wasn't updated for a long time. Fortunately, libunicows can be found on
the net.
The text in the FAX is addressed to porters and it's likely 5 years
old. No one has
Marek informed me we have these flags:
--with-profile2=no
--with-profile4=no
I have updated the documentation here:
http://www.mono-project.com/Unsupported_Advanced_Mono_Compile_Options
I would still argue we should default 4.0 to off, but at least I can
turn it off and save myself some time.
I have updated the documentation here:
http://www.mono-project.com/Unsupported_Advanced_Mono_Compile_Options
I would still argue we should default 4.0 to off, but at least I can
turn it off and save myself some time. :)
It should be off by default; It is not ready for mass use anyways.
Can we please add a --enable-profile1 as well?
-g
On 15-Jun-09, at 3:24 PM, Miguel de Icaza wrote:
I have updated the documentation here:
http://www.mono-project.com/Unsupported_Advanced_Mono_Compile_Options
I would still argue we should default 4.0 to off, but at least I can
turn it off
Can we please add a --enable-profile1 as well?
Not worth it; We need this to bootstrap, and without the bootstrap
phase we have to do a whole load of work.
Profile 1.0 is going to go away anyways at some point in the future
(Mono 2.6 might be the last release with 1.0).
miguel.
On 15-Jun-09, at 3:43 PM, Miguel de Icaza wrote:
Can we please add a --enable-profile1 as well?
Not worth it; We need this to bootstrap, and without the bootstrap
phase we have to do a whole load of work.
Profile 1.0 is going to go away anyways at some point in the future
(Mono 2.6 might
We have a .csproj file with 3000 + embedded resources. With the
current version of driver.cs (r135520 and later) on Mac OS X, we¹re getting
the following error.
Unhandled Exception: System.IO.IOException: Too many open files
at System.IO.FileStream..ctor
17 matches
Mail list logo
