[Mono-dev] Upgrade dependencies for VS build

[Jon Chambers]

Two quick questions. I'm planning on making some changes required for eglib
to build on Windows (via cygwin and VS). The long term goal of this would be
so I can get mono to build on Win64, and I think porting eglib will be
easier than glib (someone correct me if I am wrong). Is it better for mono
to use glib functions on windows, and put the windows specific stuff in
eglib, or should the windows specific calls be put in both eglib and mono?

Also, per the thread above regarding c runtimes, is there a plan to use
eglib as default on windows at some point in the future?

Thanks,
Jonathan

On 9/15/06, Jon Chambers <joncham at gmail.com> wrote:
>
> Sorry, you are correct. It seems that glib is currently being built with
> VS 6. I guess more investigation could be done, but if eglib could be made
> to work it would be much easier IMO. I had made a modification or two
> previously to get it to build in cygwin, but haven't tried in VS.
>
> - Jonathan
>
> On 9/15/06, Michael Jerris <mike at jerris.com> wrote:
> >
> > >From: Jon Chambers [mailto:joncham at gmail.com]
> > >Sent: Friday, September 15, 2006 11:30 AM
> > >To: Michael Jerris
> > >Cc: Mono Devel List
> > >Subject: Re: [Mono-dev] Upgrade dependencies for VS build
> > >
> > >As far as the version, the current glib depends on c runtime version
> > 7.0.2600.2180. The newest glib depends on the same one. As the >previous
> > version is working (somehow in VS 2005), I'd assume the newest version
> > would continue working?
> >
> > Glib itself will not have a specific dependency on a specific runtime,
> > it is linked to a specific version at compile time.  If it is currently
> > working with the current build with vs2005, you have been lucky so far,
> > pass a file handle from glib using 7.0 runtime to something built with
> > 2005, and you will see instant segfault when you try to use that handle.
> > That is just the most obvious issue, there are several more subtle ones
> > as well.
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20061018/3897c02a/attachment.html