[Mono-dev] Mono.lib on Windows

[Robert Jordan]

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 at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list