From: MikkelFJ <mikkelj-anti-spam@...1.dknet.dk>
Date: 2001-10-04T20:07:15+09:00
Subject: [ruby-talk:22077] Re: Flogging a live Window


"Eli Green" <eli.green@codedogs.ca> wrote in message
news:20011004043744.A8200@codedogs.ca...


> http://starship.python.net/crew/kernr/mingw32/Notes.html

This is great.

> See my recent comments on the Wiki about the separation of the user
> distribution and the (module) developer's distribution:
> http://www.rubygarden.org/ruby?FutureWindows

I agree with you comments at the Wiki.

If possible, I still think we should ensure that core Ruby compiles equally
well with both the gcc and VC compilers. This makes it easy to embed Ruby in
either enviroment.

> There is one problem ... and if there are any Windows people with a
solution
> to this out there, I'd love to hear it ... exported symbols in a Windows
DLL
> need that damned __declspec(dllexport) in front of them! And I sure as
hell
> don't want to be the one who has to insert that in front of every public
> function in the ruby source ... so if somebody knows how to force LINK.EXE
to
> export every symbol (like ld does), that'd be very welcome information.

This needs some thought. Dll functions also have caseinsensitive naming.
And it isn't exactly effecient if every minor Ruby support function lives in
another dll.
The best solution is to use a static library - but that can be difficult
with extension modules.

> > I'm still not convince of the incompatibility of linker format, I still
see
me neither - this is the first time I here that there is compatibility.

Mikkel