: 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 use, as Gerald already mentioned -
I'm
still thinking about
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.
-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
- Original Message -
From: Guy Harris [EMAIL PROTECTED]
To: Developer support list for Wireshark wireshark-dev@wireshark.org
Sent: Wednesday, December 20, 2006 2:36 AM
Subject: Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a
bitoutdated ...
However, I seem to remember
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
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 packages
