[Mono-devel-list] MSVC port in progress, a couple questions

[Paolo Molaro]

On 02/10/05 J Lothian wrote:
> First, just wanted to let everyone know that I'm working on getting
> Mono compiling in MSVC.  I've mainly been working in VC 6, but ran

Great!

> into a couple conflicts with source that required the updated platform
> SDK.  I get undefined errors without the SDK, and problems with some
> of the SDK headers when it is included, something to due with defining
> the platform your targetting, I believe.  I'll post errors if anyone
> thinks they can help with it, but barring that I'll be trying it in

Error messages may help or give a clue to people that might know the answer.

> To speed up my project creation though, I was wondering if anyone had
> a dependancy tree for the libraries, and/or a list of the libraries
> themselves.  I've been able to piece together most of it by reading
> through makefiles, I just want to make sure I'm not missing anything.

You might want to read the toplevel configure.in and the win32 makefile
in libgc, too.
With automake we use helper libraries, but there is no reason you need to
do the same: if you can, you should just build almost all the files into
a mono.dll shared lib. Anyway, the helper libs we use are:

libgc/libmonogc.la
mono/utils/libmonoutils.la
mono/os/unix/libmonoos.la // you want the win32 version here
mono/os/libmonoos.la
mono/metadata/libmetadata.la
mono/metadata/libmonoruntime.la
mono/mini/libmono.la

You should just skip mint and the arch directory and the other libs that
aren't important for a first cut. The libs first on the list are
usually pre-reqs for libs further down.
At the end of the process there should be only one shared library,
mono.dll. All the others are just built only as temporary libs
used by the build tools like genmdesc.

lupus

-- 
-----------------------------------------------------------------
lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better