- add it as an optional package to install when installing Cygwin
- de-duplicate some text about why it's good to work with the Subversion
source (no need to tell them the same thing, once for each Subversion
client)
- Make it obvious that the user has a choice of Subversion clients
- Fix the URL to TortoiseSVN
svn path=/trunk/; revision=46016
value in a human-readable format. Use it in the welcome screen, status
bar, and Win32 interface details.
Note that in the welcome screen and status bar we've switched from
customary binary prefixes to strict SI.
svn path=/trunk/; revision=45453
with Visual Studio Express Edition - the resulting package cannot be
self-contained and will require that the Visual C++ Redistributables be
installed on any machine into which you plug the portable Wireshark
package, which kinda defeats the purpose of a portable package (plug it
in and go).
svn path=/trunk/; revision=45315
and vcredist_{processor}.exe into three paragraphs, and put the bit
about vcredist_{64-bit processor}.exe into the paragraph about 64-bit
targets.
svn path=/trunk/; revision=45311
*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
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
Refer to the SDK as just the SDK, not the Platform SDK - Microsoft
dropped the "Platform" with the Vista SDK.
Update the section on the SDK to reflect that and to reflect that Vista
isn't the current version.
svn path=/trunk/; revision=45077
Pascal Quantin