- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Wednesday, December 20, 2006 2:36 AM
Subject: Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a
bitoutdated ...
> However, I
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Guy Harris
> Sent: 20 December 2006 10:36
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Microsoft Visual C Version 6
> support is a bitoutdated ...
Douglas Pratley wrote:
> We went through upgrades from MSCV 6 -> 7.1 -> 8 in my last job. The
> only real problem we ran into (apart from all the code tweaks in the C++
> to make it compile 6 -> 7.1, which is not relevant here) was in passing
> dynamically allocated memory across binary boundaries.
Douglas Pratley wrote:
> We went through upgrades from MSCV 6 -> 7.1 -> 8 in my last job. The
> only real problem we ran into (apart from all the code tweaks in the C++
> to make it compile 6 -> 7.1, which is not relevant here) was in passing
> dynamically allocated memory across binary boundaries.
amping
> Sent: 20 December 2006 00:51
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a
> bitoutdated ...
>
> Gerald Combs wrote:
> > Ulf Lamping wrote:
> >
> >> The biggest hurdle seems to
o: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a
bitoutdated ...
Gerald Combs wrote:
> Ulf Lamping wrote:
>
>> The biggest hurdle seems to be the different msvcrt.dll (C runtime
>> library) versions for the libs we
Gerald Combs wrote:
> Ulf Lamping wrote:
>
>> The biggest hurdle seems to be the different msvcrt.dll (C runtime
>> library) versions for the libs we use, as Gerald already mentioned - I'm
>> still thinking about the possibilities to solve this.
>>
>
> If we need to we can split the packa
Ulf Lamping wrote:
> The biggest hurdle seems to be the different msvcrt.dll (C runtime
> library) versions for the libs we use, as Gerald already mentioned - I'm
> still thinking about the possibilities to solve this.
If we need to we can split the packages subdirectory in
wireshark-win32-libs
Kukosa, Tomas wrote:
> Hi!
>
> I hope support of MSVC 6 will remain ;-)
>
I don't tend to break it - as I will also use it from time to time ;-)
> Will we have common makefile for both versions or one for each of them?
>
My goal is to have a single compiler setting in config.nmake and using
-dev@wireshark.org
Subject: [Wireshark-dev] Microsoft Visual C Version 6 support is a
bitoutdated ...
Hi List!
We currently only "support" MSVC Version 6 for the Windows builds.
As Version 6 is pretty much outdated and it's possible that I won't have
access to such an inst
10 matches
Mail list logo
