aboutsummaryrefslogtreecommitdiffstats
path: root/docbook
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2012-10-03 07:20:32 +0000
committerGuy Harris <guy@alum.mit.edu>2012-10-03 07:20:32 +0000
commit5ed58aa3a7fd1536f01eb01b0fc0453585a01db4 (patch)
tree123c59f1facfceef4ae9f13d7163e5d73a87901d /docbook
parent3fbfed9c5b8d5fdca8e3cfc617aeca527a141ae6 (diff)
Move the stuff about setting environment variables to the "setting up
cmd.exe" section. svn path=/trunk/; revision=45277
Diffstat (limited to 'docbook')
-rw-r--r--docbook/wsdg_src/WSDG_chapter_quick_setup.xml33
1 files changed, 17 insertions, 16 deletions
diff --git a/docbook/wsdg_src/WSDG_chapter_quick_setup.xml b/docbook/wsdg_src/WSDG_chapter_quick_setup.xml
index 46412fa3f3..d5b45a777c 100644
--- a/docbook/wsdg_src/WSDG_chapter_quick_setup.xml
+++ b/docbook/wsdg_src/WSDG_chapter_quick_setup.xml
@@ -105,22 +105,6 @@
<para>XXX - mention the compiler and PSDK web installers -
which significantly reduce download size - and find out the
required components</para>
- <para>Wireshark development depends on several environment variables,
- particularly <varname>PATH</varname>. You can use a batch script to fill
- these in, for example
-
- <programlisting>
-<![CDATA[@echo off
-echo Adding things to the path...
-set PATH=%PATH%;.
-set PATH=%PATH%;c:\cygwin\bin
-
-echo Setting up Visual Studio environment...
-call "c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat"
-
-title Command Prompt (VC++ 2010)]]>
- </programlisting>
- </para>
<para>Why is this recommended? While this is a huge download,
the 2010 Express Edition is the only free (as in beer)
version that includes the Visual Studio integrated
@@ -361,6 +345,23 @@ title Command Prompt (VC++ 2010)]]>
<filename>C:\Programme</filename> - take this also in account where
<filename>C:\Program Files</filename> appears elsewhere. Note: You need
to repeat steps 1 - 4 each time you open a new cmd.exe!</para>
+ <para>Wireshark development depends on several additional
+ environment variables, particularly <varname>PATH</varname>.
+ You can use a batch script to fill these in, along with the Visual
+ C++ variables; for example:
+
+ <programlisting>
+<![CDATA[@echo off
+echo Adding things to the path...
+set PATH=%PATH%;.
+set PATH=%PATH%;c:\cygwin\bin
+
+echo Setting up Visual Studio environment...
+call "c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat"
+
+title Command Prompt (VC++ 2010)]]>
+ </programlisting>
+ </para>
</section>
<section id="ChToolsWin32Verify">
<title>Verify installed tools</title>