On Mon, Apr 4, 2011 at 7:12 PM, ger...@wireshark.org wrote:
Log:
On Windows, try to use an existing console for our messages. Create one if
it doesn't exist.
This does not build with MSVC2005, because AttachConsole needs
_WIN32_WINNT 0x0500.
Did we abandon MSVC2005 and older?
--
Stig
On 20/06/2011 09:58, Stig Bjørlykke wrote:
On Mon, Apr 4, 2011 at 7:12 PM, ger...@wireshark.org wrote:
Log:
On Windows, try to use an existing console for our messages. Create one if
it doesn't exist.
This does not build with MSVC2005, because AttachConsole needs
_WIN32_WINNT 0x0500.
Did
On Mon, Jun 20, 2011 at 2:07 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
I haven't tested it for this specific issue (though I have built Wireshark
for many years in this way), but I'm pretty positive that if you install a
newer SDK (use the latest 7.1) and then from your command
On 20/06/2011 13:22, Stig Bjørlykke wrote:
On Mon, Jun 20, 2011 at 2:07 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
I haven't tested it for this specific issue (though I have built Wireshark
for many years in this way), but I'm pretty positive that if you install a
newer SDK (use the
On Mon, Jun 20, 2011 at 2:35 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
In what way can't you update your build machine?
It's a production machine, and it's not my table at all.
The build is a Scheduled Task, all I get is the output.
My main build is for Solaris and OSX, which I
On 20/06/2011 14:00, Stig Bjørlykke wrote:
On Mon, Jun 20, 2011 at 2:35 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
In what way can't you update your build machine?
It's a production machine, and it's not my table at all.
The build is a Scheduled Task, all I get is the output.
My
On Mon, Jun 20, 2011 at 3:20 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
The current standard used for Wireshark releases is VS2008, can you get the
build
machine moved to that?
I may have to install a VM.
The problem is that I did not intend to use any more time on the
windows build
