Re: More on VC++ 2005

On 1/9/06, Austin Ziegler <[e-mail]> wrote:
> On 09/01/06, nobuyoshi nakada <[e-mail]> wrote:
> > At Sat, 7 Jan 2006 03:48:02 +0900,
> > Austin Ziegler wrote in [ruby-core:07069]:
> > > The patches look good on 1.8.4.
> > Thank you.
>
>
> > > It would be *nice* to be able to have the manifest stuff automatically
> > > applied to the .so files as well, just in case, but since they depend
> > > on Ruby or the msvcr80-ruby18.dll (which *does* have the manifest
> > > applied), that should be good enough. It's probably worth documenting
> > > somewhere, though.
> > Documentation for what, to whom, and how?
>
> Mmmm. I think embedders who want to use VS2005 or later to compile
> Ruby and their programs.
>
> I did a little further looking, and I'm a little disheartened by the
> build process in Windows and I'd like to try to figure out what we
> could do to significantly improve it -- or maybe see if I can find the
> build script(s) used by usa to build everything in the ruby-mswin32
> download. Currently, the Windows installer downloads zlib separately
> and compiles it. I haven't looked much further, but I suspect that it
> does the same with a couple of other "built-in" libraries. I really
> want to be able to build these libraries from an unpacked tarfile, and
> am not sure where to go from here.

This probably isn't relevant to your current line of inquiry, but I'm
changing the way I build the One-Click Ruby Installer for Windows.
Starting with the next release its going to be based upon
ruby-mswin32, with additional extension and the installer layered on
top. This also means that I'm going back to VC++ 6.0 so that
everything will be compatible.

I do still have to download an compile zlib.

Curt