On 05/01/06, nobuyoshi nakada <nobuyoshi.nakada / ge.com> wrote:
> At Thu, 5 Jan 2006 12:38:05 +0900,
> Austin Ziegler wrote in [ruby-core:07055]:
> > 1. The zlib team recommends that you only compile to zlib1.dll if you
> > are linking against msvcrt.dll, because of zlib's intended status as a
> > "system component". As such, I am creating ruby-zlib1.dll. How can I
> > tell Ruby that's the version of zlib to compile against for zlib.so?
> --with-zlib=ruby-zlib1 might work, if you have ruby-zlib1.lib.

Hm. How would I do that, assuming that I'm starting from win32/configure.bat ?

I'm really not trying to be dumb here, I'm just not getting it. I'm
only able to spend a little bit of time on this a day, and certain
things aren't very clear for me.

> > 2. The dynamic discovery of DLLs is harder. It is possible to put
> > msvcr80.dll in the Ruby bin/ directory, but it is not the recommended
> > way to do it, since msvcr80.dll is intended to be an SxS
> > (side-by-side) assembly. I have made modifications to the Zlib and
> > OpenSSL build processes (and now pdcurses, too) to make this happen,
> > but the Ruby build process is a little too... confusing to me to deal
> > with. Basically, there's a link step and a post-link step. After the
> > link is done, a .manifest file is generated, e.g.:
> >
> >   ruby.exe
> >   ruby.exe.manifest
> >   msvcr80-ruby18.dll
> >   msvcr80-ruby18.dll.manifest
> >
> > Don't ask my *why*, but the linker doesn't give the ability to
> > automatically embed the manifest in the DLL or the EXE. However, there
> > is a way to do it using mt ("manifest tool").
> Where's that mt command?  I've installed VC++ 2005 Express
> Edition too, but can't find it anywhere.

It's part of the .NET SDK, as it's mostly meant for .NET assemblies.

I am trying to build with your Makefile.sub patches applied manually.

-austin
--
Austin Ziegler * halostatue / gmail.com
               * Alternate: austin / halostatue.ca