Re: [Mono-dev] Presentation Framework

2012-11-14 Thread Alistair Leslie-Hughes

Hi Atsushi,

On 14/11/2012 4:11 AM, Atsushi Eno wrote:

Hi,

We wouldn't bring WPF into mono tree unless it becomes usable and solid
to some extent. There may be incomplete libraries but that does not
justify bringing extraneous components into mcs build.
Actually I don't think there is considerable difference between mono and
olive to create patches. But if you really have reason, share it, I'm
personally all ears :)


Any chance on getting the olive tree updated to the latest mono?  Or
instructions on how to pull the specific patches for WPF support into my 
tree.


Best Regards
 Alistair Leslie-Hughes

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Is the `sizeof` opcode doing the right thing?

2012-11-14 Thread Robert Jordan

On 14.11.2012 04:04, Jordan Earls wrote:

Hi, I've been messing with building a rather low-level datastructure
to avoid the Large Object Heap.

One thing this required of me was to write a very small library
directly in IL. The function I implemented is this:

 .method public static hidebysig
default int32 SizeOfT ()  cil managed
 {
 .maxstack 1
sizeof !!T
  ret
 }


Have you verified this code with PEVerify under MS.NET?


In the ECMA spec, on page 423 for partition III, it says For a
reference type, the size returned is the size of a reference value to
the corresponding type, not the size of the data stored in objects
referred to by a reference value

I think that language is a tiny bit ambiguous. Basically, does this
mean mono is being correct in that it's storing a reference value as
the entire class(an optimization?), or is Mono doing the wrong thing
in not returning just the size of the pointer? I'm not sure about the
Mono internals or anything, so I suspect that it *might* be conforming
to the spec, but I'd really like if someone could verify for this for
me.


According to BCL's specs, OpCodes.Sizeof only applies to
value types:

http://msdn.microsoft.com/en-us/library/system.reflection.emit.opcodes.sizeof%28v=vs.110%29.aspx

The C# sizeof operator doesn't allow reference types either.

Robert


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


[Mono-dev] mono head build problem: System.Reactive.Interfaces.dll strong name problem

2012-11-14 Thread Jonathan Shore
Mono installation problem.  Looks like the System.Reactive assemblies are not 
signed properly:

Failure adding assembly 
./../../class/lib/net_4_5/System.Reactive.Interfaces.dll to the cache: Strong 
name cannot be verified for delay-signed assembly

Can someone check in the fix, thanks.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


[Mono-dev] problem with loading System.Windows.Forms.XplatUI on osx mono 3.0.1

2012-11-14 Thread Jonathan Shore
I am trying to run a simple WinForms application (verified to work on windows 
and Linux mono 3.0.x).   For whatever reason, mono has a problem attaching to 
or finding the libc shared lib:

System.TypeInitializationException: An exception was thrown by the type 
initializer for System.Windows.Forms.XplatUI --- System.DllNotFoundException: 
libc.dylib
  at (wrapper managed-to-native) System.Windows.Forms.XplatUI:uname (intptr)
  at System.Windows.Forms.XplatUI..cctor () [0x0] in filename unknown:0 
  --- End of inner exception stack trace ---
  at System.Windows.Forms.Application.EnableVisualStyles () [0x0] in 
filename unknown:0 
  at ExecutorUI.Program.Main () [0x0] in filename unknown:0 

However, libc.dylib is in the usual expected location and has both the i386 and 
x86_64 architectures.

$ file /usr/lib/libc.dylib 
/usr/lib/libc.dylib: Mach-O universal binary with 2 architectures
/usr/lib/libc.dylib (for architecture x86_64):  Mach-O 64-bit dynamically 
linked shared library x86_64
/usr/lib/libc.dylib (for architecture i386):Mach-O dynamically linked 
shared library i386

$ $ mono --version
Mono JIT compiler version 3.0.1 (master/301b6c6 Mon Nov  5 14:45:52 EST 2012)
Copyright (C) 2002-2012 Novell, Inc, Xamarin Inc and Contributors. 
www.mono-project.com
TLS:   normal
SIGSEGV:   altstack
Notification:  kqueue
Architecture:  x86
Disabled:  none
Misc:  softdebug 
LLVM:  yes(3.1svn-mono)
GC:Included Boehm (with typed GC)



2.10.9 does not fail, but does not completely render the app, giving a repeated 
error:

/Library/Frameworks/Mono.framework/Versions/2.10.9/bin/mono ExecutorUI.exe
Nov 14 21:00:30 karma.local mono[10194] Error: CGBitmapContextCreateImage: 
invalid context 0x0
Nov 14 21:00:30 karma.local mono[10194] Error: CGBitmapContextCreateImage: 
invalid context 0x0
...

I have not tried this on 2.10 on Linux, rather using 3.0.x.  

Ideas on how to fix the mono 3.0.1 issue?   

Thanks
Jonathan___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


[Mono-dev] Compile error with debuild on Ubuntu

2012-11-14 Thread Adam Baxter
Hi guys,
I'm trying to build mono from Git on Ubuntu with debuild and I'm getting
errors at the last build-step.

Cannot open assembly 'mcs/class/lib/net_4_0/dmcs.exe': No such file or
directory.

The complete log is about 1.9mb. I've posted it at
https://raw.github.com/gist/4076563/c87b7177d5ed691003442eed6a38b392ad310016/gistfile1.txtbut
if you want me to gzip it and post it to the list let me know.

The only changes I have made are to remove a debian symbol check step as
the debian packaging files are out of date.

I also needed to use the monolite files to make the compile work at all

My build command was EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/gmcs.exe
debuild -j5 -b

Any ideas?

Thanks,
Adam Baxter
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


Re: [Mono-dev] mono head build problem: System.Reactive.Interfaces.dll strong name problem

2012-11-14 Thread Atsushi Eno
I've been fixing the build. Sorry for inconvenience. You can check 
https://wrench.mono-project.com/Wrench/ for ongoing fixes.


In the end of this fixage, Reactive Extensions will be available in mono.

Atsushi Eno

Jonathan Shore wrote:

Mono installation problem.  Looks like the System.Reactive assemblies are not 
signed properly:

Failure adding assembly 
./../../class/lib/net_4_5/System.Reactive.Interfaces.dll to the cache: Strong 
name cannot be verified for delay-signed assembly

Can someone check in the fix, thanks.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list





___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list