*all* 64-bit builds, regardless of whether you have Visual Studio Express
Edition or not.
You only need to download the redistributable package when you're using
the Express Edition or are doing 64-bit builds.
svn path=/trunk/; revision=45307
MSVC2008 and MSVC2010, when doing 32-bit builds, with the non-Express
versions we "Install a particular Visual C++ assembly as a private
assembly for the application", if for no other reason than to support
"portable" versions of Wireshark, where the application is provided a a
completely self-contained directory tree on a medium such as a flash
drive, and where there is no installer to install anything on the target
machine. For 64-bit builds, we currently don't support a "portable"
version, so we "Use the Visual C++ Redistributable Package".
Convert tabs to spaces.
svn path=/trunk/; revision=45306
the versions of vcredist, just in case anybody is building for Itanium.
The second time we mention them, mention all three, not just the 32-bit
x86 version. Rewrite the sentence for that a bit - it's not as if MSVC
uses particular deployment methods, those were chosen by the Wireshark
development team.
For VS 2008, note that Microsoft mentions all three redistribution
mechanisms, and link to the "Choosing a Deployment Method" page for VS
2008 (which looks as if Microsoft didn't do a good job of editing it
after copying-and-pasting the 2005 version, or didn't set up ASP or
whatever it is that supplies VS-specific versions of the pages
correctly).
For VS 2010, note that Microsoft mentions all three redistribution
mechanisms, link to the "Choosing a Deployment Method" page for VS 2010,
and note that it recommends the method we chose and gives it as as the
first method.
svn path=/trunk/; revision=45302
tags from the "Redistributing Visual C++ libraries" section of the MSDN
"Choosing a Deployment Method" page, and put them in the same order as
the three methods mentioned on that page (which means swapping the
second and third ways in the list, so "method 2" becomes "method 3" and
"method 3" becomes "method 2".
svn path=/trunk/; revision=45301
shared "file_add_extension" routine. We no longer support _MSC_VER <
1400 so get rid of some clutter. Add a gzip checkbox to the Win32 export
packets dialog. Windows code hasn't yet been tested (and is likely
broken). I'll fix it shortly.
svn path=/trunk/; revision=45296
This fixes gcc compiler errors [-Werror=unused-result] caused by the recent addition
of the "__wur" (warn_unused_result) attribute to the declarations of these functions in
unistd.h.
svn path=/trunk/; revision=45286
it should also fix bulding error:
Can't open ../../doc/reordercap.pod: No such file or directory at /usr/bin/pod2man line 60
svn path=/trunk/; revision=45283
paragraphs give more details on how to install, and the stuff about
vcvars32.bat is given later, in more detail.
While we're at it, fix another reference to vcvars32 to also refer to
vcvarsall.
svn path=/trunk/; revision=45278
the "32-bit vs. 64-bit build machine" vs. "32-bit vs. 64-bit target"
matrix. Use the correct paths ("Visual Studio 10.0", not "Visual Studio
10" - an MSDN page uses the latter, but my virtual machine shows the
former; add "(x86)" to "Program Files" on 64-bit machines, as the batch
files are installed in 32-bitland).
svn path=/trunk/; revision=45276
host_name_lookup_process(). If, in the future, we find that we need an
argument for changes we're making, we can add it then.
svn path=/trunk/; revision=45269
comment out the older, conflicting ETSI-specified values and use the more
modern ones.
Mark a couple of deprecated values as such (void).
svn path=/trunk/; revision=45251
Guy Harris