Wireshark-dev: Re: [Wireshark-dev] Win32: remove binary zlib.dll completely and compile it for
From: "Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx>
Date: Mon, 16 Jul 2007 08:35:38 -0700

----- Original Message ----- From: "Ulf Lamping" <ulf.lamping@xxxxxx>
To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
Sent: Friday, July 13, 2007 6:05 PM
Subject: Re: [Wireshark-dev] Win32: remove binary zlib.dll completely and compile it for all MSVC variants?


Gerald Combs schrieb:
Ulf Lamping wrote:

I know I'm asking you to do yet more work, but I think adns needs the same
treatment.


Better make a policy change and implement that. Is 2005EE the way to go?

The zlib thing is about to remove a MSVC 6 specialty that can be done by the way 2005EE is already working and adns will be much the same.

So we're already heading exactly in the 2005EE direction and dropping support for MSVC 6 won't save us a lot of effort.

I'm not opponing against an "official" switch to 2005EE, but I don't see this topic as "the reason" for it :-)


Is it possible to to build a U3 package using 2005EE without making the
user run the Visual C++ Redistributable Package (vcredist_x86.exe)
AFAIK, the redistributable files required (e.g. msvcr80.dll and alike
two or three files) are only part of the commercial MSVC 2005, but not
of the Express Edition (or there's no redistributable note coming with
it, which could make it legally problematic).

It might be possible to put the redistributable files from MSVC 2005 on
the wireshark.org server, so anyone could simply add these dll's to the
installer which then goes to c:\program files\wireshark, so they are
there on the end system.

However, I just don't know if it's technically (I didn't tested it) or
legally (the MS redistributable agreement might prevent this) possible -
so there are many "if's" in this, but it may be possible.

It should be possible, from what I've read on some MS employee blogs (one of the people responsible for WinSxS). In any I haven't been able to copy the right files and have the proper manifests so that wireshark will load the CRT DLLs from the local folder instead of yelling because of some missing component.

Have a nice day
GV



Regards, ULFL

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev