[Mono-dev] Opening mono sln files in vs2008
Hi, I have been trying to open the library implementations ( System.Web.Services ) System.Web.Services20.sln file in visual studio 2008 and it says it cannot open the csproj files as they are not compatible. Which visual studio will open these files ( I also tried with vs2005). Thanks /Saurav ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] ListBox.cs ownder draw variable size
Handles calculation if the listbox scroll area of variable high, owner
draw boxes,
Index: Managed.Windows.Forms/System.Windows.Forms/ListBox.cs
===
--- Managed.Windows.Forms/System.Windows.Forms/ListBox.cs(Revision
103872)
+++ Managed.Windows.Forms/System.Windows.Forms/ListBox.cs(Arbeitskopie)
@@ -2145,9 +2145,20 @@
last_visible_index = LastVisibleItem ();
int diff = top_item - top_index;
-
+int delta = ItemHeight * diff;
+if (DrawMode == DrawMode.OwnerDrawVariable) {
+delta = 0;
+if ( top_index top_item ) {
+for ( int i = top_index; i top_item; i++ )
+delta += GetItemHeight(i);
+}
+else {
+for ( int i = top_item; i top_index; i++ )
+delta -= GetItemHeight(i);
+}
+}
if (IsHandleCreated)
-XplatUI.ScrollWindow (Handle, items_area, 0, ItemHeight
* diff, false);
+XplatUI.ScrollWindow (Handle, items_area, 0, delta, false);
}
#endregion Private Methods
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono C# Serial Port problem
Alan_Chun wrote: HI, currently I am porting a windows app to linux using Mono. I have some difficulties to get the serial port work. here is the code(based on mono website): I have also tried BytesToRead, Read, ReadByte, all of them are working fine under windows using .net2.0 framwork. But once I use the mono runtime, the nightmare begins. Any help will be really apprecaited! Thanks I'm actually having the same problem. I'm using ubuntu 8.04. -- View this message in context: http://www.nabble.com/Mono-C--Serial-Port-problem-tp17241892p17530860.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] ResourceReader patch
Hello all,
Since both ResourceInfo and ResourceCacheItem are used for caching, I think
they are not created a lot. Thus I don't think their creation/collection
pose a pressure on GC.
In the same time ResourceReader can be under heavy pressure and utilize its
cache a lot.
Once the cache data is converted to a struct their is a great potential that
it will be boxed somewhere (see Andy's comments below) and this may happen
in a common flow.
I'm not convinced that there is a performance improvement, and there is a
great potential that after this optimization the performance will even
degrade.
On Thu, May 29, 2008 at 12:59 PM, Andy Hume [EMAIL PROTECTED] wrote:
For full no-allocation behaviour :-) the IList passed to
LoadResourceValues needs to be typed as its real Generic type, otherwise
ResourceCacheItem is boxed on store.Add. Don't know how often that
operation occurs...
Andy
e.g. [[
Index: ResourceReader.cs
===
--- ResourceReader.cs (revision 104379)
+++ ResourceReader.cs (working copy)
@@ -409,7 +409,11 @@
return obj;
}
+#if NET_2_0
+ void LoadResourceValues (IListResourceCacheItem store)
+#else
void LoadResourceValues (IList store)
+#endif
{
ResourceInfo ri;
ResourceCacheItem rci;
]]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Marek Habersack
Sent: 28 May 2008 22:36
To: mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] ResourceReader patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 May 2008 10:21:19 +0200
Andreas Nahr [EMAIL PROTECTED] wrote:
Is there any reason for not using structs?
No sense in needlessly torturing the GC ;)
Makes sense - applied in r104334, thanks!
marek
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIPdA1q3909GIf5uoRAlsvAJ98jcbhTtuNUudBHybCR4xBCD3k1QCfYngI
Qougwstb8DzXROt6uTn7aHc=
=Gris
-END PGP SIGNATURE-
___
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
--
Regards,
Konstantin Triger
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Source of regressions in System.Xml
Hey Andreas, hey Gert, You might be interesting in a bug I just filed: https://bugzilla.novell.com/show_bug.cgi?id=395904 It shows where the regressions in System.Xml are coming from when enabling this code in String.Substring: // FIXME: this causes regressions in System.Xml /* if (startIndex == 0 length == this.length) return this; */ By the way: Thanks for the excellent rewrite of the String class, it's great to have all that code in the managed world! - Juraj ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Source of regressions in System.Xml
Hey Juraj, Yeah, I saw your report. Thanks for taking time to find the cause! As for the managed code rewrite: all credit goes to Andreas for that. Gert -- From: Juraj Skripsky [EMAIL PROTECTED] Sent: Friday, May 30, 2008 7:02 PM To: Andreas Nahr [EMAIL PROTECTED]; Gert Driesen [EMAIL PROTECTED] Cc: mono-devel-list@lists.ximian.com Subject: Source of regressions in System.Xml Hey Andreas, hey Gert, You might be interesting in a bug I just filed: https://bugzilla.novell.com/show_bug.cgi?id=395904 It shows where the regressions in System.Xml are coming from when enabling this code in String.Substring: // FIXME: this causes regressions in System.Xml /* if (startIndex == 0 length == this.length) return this; */ By the way: Thanks for the excellent rewrite of the String class, it's great to have all that code in the managed world! - Juraj ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono C# Serial Port problem
Hi, I hope to have our OSX implementation up in the next couple of days. This implementation should work under linux too!! I am also looking at the serial.c source and will try to get that to work under OSX as well. I will send the link ASAP. Shawn Schaerer Director of Research and Development Cogmation Robotics Inc www.cogmation.com On 30-May-08, at 12:03 PM, [EMAIL PROTECTED] wrote: Alan_Chun wrote: HI, currently I am porting a windows app to linux using Mono. I have some difficulties to get the serial port work. here is the code(based on mono website): I have also tried BytesToRead, Read, ReadByte, all of them are working fine under windows using .net2.0 framwork. But once I use the mono runtime, the nightmare begins. Any help will be really apprecaited! Thanks I'm actually having the same problem. I'm using ubuntu 8.04. -- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Newbie guide to debugging class libraries?
Newbie alert! You have been warned. I'm trying to debug some potential bugs in the class libraries and have hit a wall. From what I have gleaned from mono-project.com, there seem to be two ways of doing this. 1) Build and debug using MSVS 2) Build with mono, debug with mdb First I tried option 1, and found that some assemblies have project files that load in VS (SWF for example), but many do not. I would like to try the second option, but can't figure out how to debug a class library build from the make files. Basically I'm looking for documentation on a day in the life of a mono class library developer. If that does not exist, could someone please answer the following? - What is the preferred method of debugging mcs libraries? - How do I make a debug build of a class library? - How do I build the NUnit tests? Thanks, -Tom ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Newbie guide to debugging class libraries?
Hello Tom, 2008/5/30 Tom Cannon [EMAIL PROTECTED]: First I tried option 1, and found that some assemblies have project files that load in VS (SWF for example), but many do not. I would like to try the second option, but can't figure out how to debug a class library build from the make files. I run into a similar issue while debugging WCF stuff under VS. I wrote a small guide within Mono wiki: http://www.mono-project.com/Debugging_Tips_for_Windows. It may apply for you. Cheers, -- Marcos | http://www.youcannoteatbits.org ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [PATCH] Update to Winx64 stack patch
I have updated this patch based off a discussion with Zoltan on IRC. -bill On Wed, May 28, 2008 at 11:00 AM, Bill Holmes [EMAIL PROTECTED] wrote: I have a small patch that seems to have fix a bunch of issues with the unit tests under mono/tests for Windows x64. Please review and let me know if I am headed in the right direction. I am still a bit lost in this code but I fell that I am learning. ;) There are still a small number of tests failing that I am looking at. The first set I will be tackling are the ones that call into libtest.so (or dll.) I will be adding a build project to the VS solution for this dll next. I will also be doing some cleanup in the VS solution and projects to make the output directories more uniform. This is in preparation for adding a vsbuild target to the current cygwin make process that Jonathan and Miguel discussed in an earlier thread. -bill mini-amd64_x64_stack_align.diff Description: Binary data ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Strange GdkSharp.PixbufDestroyNotifyWrapper error..
Hi guys: I have a simple code in a gtk window that use a pixbuf to put some image in a widget that inherit from DrawingArea, then at some point I call to the SetSizeRequest function and I get a really weird InvalidProgramException..the widget is associate internally to the OnExposeEvent, the handler is reached but then when I call to function that update a internal Pixbuf (still not doing nothing with the widget, just the function that update de pixbuf that is used later in the handler to update the draw of the drawingarea) the app crash with a: ExcObject: System.InvalidProgramException: Invalid IL code in (wrapper native-to-managed) GdkSharp.PixbufDestroyNotifyWrapper:NativeCallback (intptr,intptr): IL_0030: call 0x0006 at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_delegate_to_ftnptr (object) at (wrapper managed-to-native) Gdk.Pixbuf:gdk_pixbuf_new_from_data (byte[],int,bool,int,int,int,int,GdkSharp.PixbufDestroyNotifyNative,intptr) at Gdk.Pixbuf..ctor (System.Byte[] data, Colorspace colorspace, Boolean has_alpha, Int32 bits_per_sample, Int32 width, Int32 height, Int32 rowstride, Gdk.PixbufDestroyNotify destroy_fn) [0x0] I use GLib.ExceptionManager.UnhandledException to get that little info :-S The weird thing is that with exactly the same code with mono-1.2.6 work like a charm and now the problem show up after a update to mono-1.9.1-3.1... any ideas?, I don't know even where to start...what that kind of message mean to begin to figure out what is happening?, some rule change to deal with pixbuf and that kind of types from mono-1.2.6 ? Thanks. Mauricio ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [PATCH] Mono DTrace provider v2
Hello,
Here's an updated version of my patch, adding initial DTrace support
to the Mono runtime.
A new hand-crafted header file has been added, which is to be included
in place of the generated header file. It defines MONO_PROBE_* macros
as requested by Zoltan. The generated header file is then only needed
iff DTrace is enabled.
Ugly build steps for Solaris were moved to a shell script. It extracts
object files from their library to a temporary directory, patches them
and puts them back in. This helps keep Makefiles clean and provides a
one-stop resource to fix things, should they break. Tested on
OpenSolaris 2008.05 i86. (Warning: I am not experienced in writing
shell scripts.)
It appears the problem with the gc-end probe on Solaris was due to
some kind of compiler optimization or the like. Adding a trailing
sleep(0) call made it work; I have limited this workaround to when the
gc-end probe is enabled on Solaris, to minimize the impact. Better
ideas welcome. If we do stick with it and it turns out this is needed
in more void functions, we could consider turning this into a
MONO_PROBE_* macro to keep source files clean.
Signed-off-by: Andreas Faerber [EMAIL PROTECTED]
Change Log v2:
* dtrace-prelink.sh.in: New
Script to prevent ugly Solaris hacks in Makefiles.
* configure.in:
Prepare support for OSX/x86_64 (untested)
Output dtrace-prelink.sh script.
* data/mono.d: Renamed (from mono-trace.d)
Added standard Mono header.
Added generation argument to gc-{begin,end} probes.
Added explicit stability attributes.
* mono/utils/dtrace.h: New
Wrapper around generated mono/utils/mono-dtrace.h.
Define MONO_PROBE_* macros.
* mono/utils/Makefile.am:
We no longer need to postprocess the generated header file.
* mono/metadata/Makefile.am,
mono/mini/Makefile.am:
Use new dtrace-prelink.sh script.
* mono/mini/mini.c,
mono/metadata/boehm-gc.c:
Use new macros
* mono/metadata/boehm-gc.c:
Add workaround to make gc-end probe work on Solaris.
Andreas
DTrace-USDT-2.diff
Description: Binary data
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono C# Serial Port problem
Would you mind filling a bug with the precise information? Thanks, Carlos. El jue, 29-05-2008 a las 02:24 -0700, Bs360 escribió: Alan_Chun wrote: HI, currently I am porting a windows app to linux using Mono. I have some difficulties to get the serial port work. here is the code(based on mono website): I have also tried BytesToRead, Read, ReadByte, all of them are working fine under windows using .net2.0 framwork. But once I use the mono runtime, the nightmare begins. Any help will be really apprecaited! Thanks I'm actually having the same problem. I'm using ubuntu 8.04. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.lib on Windows
Wow, libmono.a is 64MB, 15 MB compressed... :( Um, maybe we could have
a win32 embedded Wiki page that describes this rather than ship 2 files
of that size in the installer?
Ideas or recommendations?
Wade
On Fri, 2008-05-30 at 18:23 -0600, Wade Berrier wrote:
Just to be sure, this was using MSVC, correct?
I'll Update the script to make a copy of libmono.a - mono.lib.
Thanks for trying this out and reporting!
Wade
On Fri, 2008-05-30 at 19:39 -0400, Bill Holmes wrote:
Wade,
I finally got around to testing using libmono.a as the library to link
on Windows and it work fine for me.
I did a simple test to call the first symbol I found in the include
directory. (See below.) I guess that is enough proof of concept.
So the answer to you questoin on Thursday to use libmono.dll.a or
libmono.a, the answer is libmono.a.
-bill
#include stdafx.h
extern C
{
#include mono-path.h
}
int _tmain(int argc, _TCHAR* argv[])
{
mono_path_resolve_symlinks ();
return 0;
}
signature.asc
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] ListBox.cs ownder draw variable size
Hey,
Two things for your next patch:
* Use the coding guidelines:
http://www.mono-project.com/Coding_Guidelines
* Send your patch as an attached file, not in the body of the message.
Committed your patch,
thanks for the correction!
Carlos.
El mié, 28-05-2008 a las 06:42 +0200, jkeymer escribió:
Handles calculation if the listbox scroll area of variable high, owner
draw boxes,
Index: Managed.Windows.Forms/System.Windows.Forms/ListBox.cs
===
--- Managed.Windows.Forms/System.Windows.Forms/ListBox.cs(Revision
103872)
+++ Managed.Windows.Forms/System.Windows.Forms/ListBox.cs(Arbeitskopie)
@@ -2145,9 +2145,20 @@
last_visible_index = LastVisibleItem ();
int diff = top_item - top_index;
-
+int delta = ItemHeight * diff;
+if (DrawMode == DrawMode.OwnerDrawVariable) {
+delta = 0;
+if ( top_index top_item ) {
+for ( int i = top_index; i top_item; i++ )
+delta += GetItemHeight(i);
+}
+else {
+for ( int i = top_item; i top_index; i++ )
+delta -= GetItemHeight(i);
+}
+}
if (IsHandleCreated)
-XplatUI.ScrollWindow (Handle, items_area, 0, ItemHeight
* diff, false);
+XplatUI.ScrollWindow (Handle, items_area, 0, delta, false);
}
#endregion Private Methods
___
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
Re: [Mono-dev] Mono.lib on Windows
Hi guys,
libmono.a is a static lib. As such, it's not suitable for embedding,
regardless of the compiler: The GC on Win32 expects to be run
from a dll. The sample below would crash if it would actually try
more than this simple function.
libmono.dll.a is the correct library to link against *when using
cygwin*, but for some reasons, this lib is not suitable for MSVC.
I've already STFW but I was not able to find the reason of this.
The only way that works seems to be MS' lib tool:
lib /nologo /machine:x86 /def:mono.def /out:mono.lib
Robert
Wade Berrier wrote:
Wow, libmono.a is 64MB, 15 MB compressed... :( Um, maybe we could have
a win32 embedded Wiki page that describes this rather than ship 2 files
of that size in the installer?
Ideas or recommendations?
Wade
On Fri, 2008-05-30 at 18:23 -0600, Wade Berrier wrote:
Just to be sure, this was using MSVC, correct?
I'll Update the script to make a copy of libmono.a - mono.lib.
Thanks for trying this out and reporting!
Wade
On Fri, 2008-05-30 at 19:39 -0400, Bill Holmes wrote:
Wade,
I finally got around to testing using libmono.a as the library to link
on Windows and it work fine for me.
I did a simple test to call the first symbol I found in the include
directory. (See below.) I guess that is enough proof of concept.
So the answer to you questoin on Thursday to use libmono.dll.a or
libmono.a, the answer is libmono.a.
-bill
#include stdafx.h
extern C
{
#include mono-path.h
}
int _tmain(int argc, _TCHAR* argv[])
{
mono_path_resolve_symlinks ();
return 0;
}
___
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
Re: [Mono-dev] Mono.lib on Windows
If this is the case we shouldn't be shipping the .a at all, as its
fundamentally useless.
Has anyone ever looked at getting boehm to run on windows without
DllMain (*I assume this is what is needs/expects. I didn't look at it
yet)
-g
On Sat, 2008-05-31 at 02:50 +0200, Robert Jordan wrote:
Hi guys,
libmono.a is a static lib. As such, it's not suitable for embedding,
regardless of the compiler: The GC on Win32 expects to be run
from a dll. The sample below would crash if it would actually try
more than this simple function.
libmono.dll.a is the correct library to link against *when using
cygwin*, but for some reasons, this lib is not suitable for MSVC.
I've already STFW but I was not able to find the reason of this.
The only way that works seems to be MS' lib tool:
lib /nologo /machine:x86 /def:mono.def /out:mono.lib
Robert
Wade Berrier wrote:
Wow, libmono.a is 64MB, 15 MB compressed... :( Um, maybe we could have
a win32 embedded Wiki page that describes this rather than ship 2 files
of that size in the installer?
Ideas or recommendations?
Wade
On Fri, 2008-05-30 at 18:23 -0600, Wade Berrier wrote:
Just to be sure, this was using MSVC, correct?
I'll Update the script to make a copy of libmono.a - mono.lib.
Thanks for trying this out and reporting!
Wade
On Fri, 2008-05-30 at 19:39 -0400, Bill Holmes wrote:
Wade,
I finally got around to testing using libmono.a as the library to link
on Windows and it work fine for me.
I did a simple test to call the first symbol I found in the include
directory. (See below.) I guess that is enough proof of concept.
So the answer to you questoin on Thursday to use libmono.dll.a or
libmono.a, the answer is libmono.a.
-bill
#include stdafx.h
extern C
{
#include mono-path.h
}
int _tmain(int argc, _TCHAR* argv[])
{
mono_path_resolve_symlinks ();
return 0;
}
___
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
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] [PATCH] Fixes for libtest.c and VS
Last patch for the week. I promise. These changes are to make libtest.c ready to be compiled in Visual Studio. I will be sending the patch for the new VS project and update to the solution. The STDCALL statements had to be moved and I added declspec(dllexport) statements to all methods. At least I hope I got them all. Sorry no ChangeLog, I will add it Monday. It is late and my wife is calling again. Thanks all and have a good weekend. -bill libtest_c_forVS.diff Description: Binary data ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono.lib on Windows
Hello,
Attached is a patch that makes the create-windef.pl script run on
Windows. We can run this as a post build step on Windows to produce the def
file, and then run Robert's lib.exe step to produce a library that people
can link against. Note that this last step requires access to Windows SDK
tools on the build machine. I have no perl skills, so if my few changes can
be improved, please do.
Contributed under MIT/X11 license.
Thanks,
Jonathan
On Fri, May 30, 2008 at 9:18 PM, Geoff Norton [EMAIL PROTECTED] wrote:
If this is the case we shouldn't be shipping the .a at all, as its
fundamentally useless.
Has anyone ever looked at getting boehm to run on windows without
DllMain (*I assume this is what is needs/expects. I didn't look at it
yet)
-g
On Sat, 2008-05-31 at 02:50 +0200, Robert Jordan wrote:
Hi guys,
libmono.a is a static lib. As such, it's not suitable for embedding,
regardless of the compiler: The GC on Win32 expects to be run
from a dll. The sample below would crash if it would actually try
more than this simple function.
libmono.dll.a is the correct library to link against *when using
cygwin*, but for some reasons, this lib is not suitable for MSVC.
I've already STFW but I was not able to find the reason of this.
The only way that works seems to be MS' lib tool:
lib /nologo /machine:x86 /def:mono.def /out:mono.lib
Robert
Wade Berrier wrote:
Wow, libmono.a is 64MB, 15 MB compressed... :( Um, maybe we could have
a win32 embedded Wiki page that describes this rather than ship 2 files
of that size in the installer?
Ideas or recommendations?
Wade
On Fri, 2008-05-30 at 18:23 -0600, Wade Berrier wrote:
Just to be sure, this was using MSVC, correct?
I'll Update the script to make a copy of libmono.a - mono.lib.
Thanks for trying this out and reporting!
Wade
On Fri, 2008-05-30 at 19:39 -0400, Bill Holmes wrote:
Wade,
I finally got around to testing using libmono.a as the library to
link
on Windows and it work fine for me.
I did a simple test to call the first symbol I found in the include
directory. (See below.) I guess that is enough proof of concept.
So the answer to you questoin on Thursday to use libmono.dll.a or
libmono.a, the answer is libmono.a.
-bill
#include stdafx.h
extern C
{
#include mono-path.h
}
int _tmain(int argc, _TCHAR* argv[])
{
mono_path_resolve_symlinks ();
return 0;
}
___
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
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
create-windef.diff
Description: Binary data
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Strange GdkSharp.PixbufDestroyNotifyWrapper error..
On Fri, 2008-05-30 at 17:00 -0400, [EMAIL PROTECTED] wrote: ExcObject: System.InvalidProgramException: Invalid IL code in (wrapper native-to-managed) GdkSharp.PixbufDestroyNotifyWrapper:NativeCallback (intptr,intptr): IL_0030: call 0x0006 I think this is a known issue with PixbufDestroyNotifyNative using a byte[] for the pixbuf parameter without the appropriate [MarshalAs] magic. I just committed a patch to gtk-sharp trunk (revision 104582) which should resolve the issue. Mike ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
