aboutsummaryrefslogtreecommitdiffstats
path: root/README.win32
diff options
context:
space:
mode:
Diffstat (limited to 'README.win32')
-rw-r--r--README.win32135
1 files changed, 67 insertions, 68 deletions
diff --git a/README.win32 b/README.win32
index 761ccbca82..b457784fa6 100644
--- a/README.win32
+++ b/README.win32
@@ -1,4 +1,4 @@
-$Id: README.win32,v 1.67 2004/04/09 07:37:25 ulfl Exp $
+$Id: README.win32,v 1.68 2004/04/10 09:10:01 ulfl Exp $
Installing Ethereal, Tethereal, and Editcap on Win32
====================================================
@@ -88,101 +88,80 @@ The rest of this documentation is only interesting if
you want to compile Ethereal yourself.
-Running Ethereal, Tethereal, and Editcap on Win32
-=================================================
-You need the glib and gtk libraries for running Ethereal.
+Compiling the Ethereal distribution from source
+===============================================
-These packages for win32 can be found at:
+Automated library download
+--------------------------
+Before using the automated download, be sure to edit the config.nmake file
+to suit your needs. Especially have a look at the ETHEREAL_LIBS setting.
+However, the defaults should be working well for a first start.
- http://www.ethereal.com/distribution/win32
+If you've installed Microsoft Visual C++ (MSVC), you can run:
-and at the home page for the GTK+ for Win32 project:
+nmake -f makefile.nmake setup
- http://www.gimp.org/~tml/gimp/win32
+This will first check the availability of all required tools and then uses
+the tool wget to download each package file (together around 30MB!) from the
+server location at:
-or
- http://www.iki.fi/tml/gimp/win32/
+http://www.ethereal.com/distribution/win32/development/
-(the mirror nearer to you may be faster).
+and unpack it in the $ETHEREAL_LIBS directory.
-Plugins (gryphon.dll and mgcp.dll) can go in:
- <Ethereal installation directory>\plugins\<version>
+If you have problems downloading the files, you might be connected to the
+internet through a proxy/firewall. In this case see the wget documentation
+to configure wget accordingly.
-Where <version> is the version number, without brackets. For example,
-if you have Ethereal 0.9.8 installed in the default location, plugins
-will reside in C:\Program Files\Ethereal\plugins\0.9.8
-Yes, the location of plugins needs to be more flexible.
+Required libraries
+------------------
+If the automated library download finished sucessfully, you should have all
+libraries on your machine at the right places. So you don't have to read this,
+unless you are interested which libraries are used.
-Make sure the glib and gtk DLL's are in your path - i.e., that your
-path includes the directory (folder) or directories (folders) in which
-those DLLs are found - when you run Ethereal. This includes gtk-*.dll,
-glib-*.dll, gmodule-*.dll, gdk-*.dll, intl.dll, and iconv-*.dll. As of
-the 20000805 GTK+/GLIB distribution, gthread-*.dll is no longer needed.
+You'll need the development packages for GLIB, GTK+, iconv, gettext,
+WinPcap, Net-SNMP, and optionally ADNS, PCRE and zlib. The development
+packages contain header files and stub libraries to link against.
-Note the wiretap*.dll must be in your path as well and if wiretap is changed
-be shure to put the new one in your path.
+PRECOMPILED VERSIONS OF ALL OF THESE PACKAGES ARE AVAILABLE AT:
-The Win32 Binary distribution, available from
+ http://www.ethereal.com/distribution/win32/development/
- http://www.ethereal.com/distribution/win32
-used different version of the GTK+/GLIB libraries at different points
-in time:
+The GLIB, GTK+, iconv, gettext packages for win32 can be found at the home
+page for the GTK+ for Win32 project:
-Ethereal Version GTK+/GLIB version
----------------- -----------------
-0.8.16 and after 20001226
-0.8.11 - 0.8.15 20000805
-0.8.9 - 0.8.10 20000416
-0.8.8 and before 19990828
+ http://www.gimp.org/~tml/gimp/win32 or the mirror
+ http://www.iki.fi/tml/gimp/win32/
+The Net-SNMP package for win32 is available at its homepage:
-Capturing Packets
------------------
-In order to capture with Win32, you need to install the NDIS
-packet capture driver for your particular Win32 OS; drivers for Windows
-9x, Windows NT 4.0, Windows 2000 and Windows XP can be downloaded from the
-WinPcap home page:
+ http://
- http://winpcap.polito.it/
-
-or the mirror site at
+The WinPcap package is available at its homepage:
+ http://winpcap.polito.it/ or the mirror
http://www.wiretapped.net/security/packet-capture/winpcap/default.htm
-Compiling the Ethereal distribution from source
-===============================================
+The optional ADNS package for win32 is available at its homepage:
-You'll need the development packages for GLIB, GTK+, iconv, gettext,
-WinPcap, zlib, Net-SNMP, ADNS, and PCRE. The GLIB, GTK+, and WinPcap
-packages are available from the respective home pages for each project
-(the same URLs as listed above). The development packages contain header
-files and stub libraries to link against. Precompiled versions of all
-of these packages are available at
+ http://adns.jgaa.com/
- http://www.ethereal.com/distribution/win32/development/
+The optional PCRE package (Perl Compatible Regular Expressions) for win32 is
+available at its homepage:
-The ADNS package is also available at its homepage:
+ http://gnuwin32.sourceforge.net/packages/pcre.htm
+
+The optional zlib package for win32 is available at its homepage:
+
+ http://www.gzip.org/zlib/
- http://adns.jgaa.com/
By default, the build process looks for these packages in
C:\ethereal-win32-libs. You can place them in a different directory, but
you must update the ETHEREAL_LIBS variable in config.nmake accordingly.
-If you're running MSVC++, you can run:
-
-nmake -f makefile.nmake setup
-
-to download each package file (together around 30MB!) and unpack it in the
-$ETHEREAL_LIBS directory.
-This will first check the availability of all required tools and then uses
-the tool wget to download the files from the server location at
-www.ethereal.com mentioned above. If you have problems downloading the files,
-you might be connected to the internet through a proxy/firewall. In this case
-see the wget documentation to configure wget accordingly.
-
The following lists the packages needed to compile Ethereal and the default
locations where to unpack them, when the above method isn't used.
@@ -223,13 +202,13 @@ Compiling the Ethereal distribution using GTK+2
The more recent version 2 of the GTK+ can be used to compile
Ethereal with, but is still considered beta.
-GTK+2 will look better and nicer in some ways, especially for WIN32 users.
+GTK+2 will look better in various ways, especially for WIN32 users.
You can get the required libraries from:
http://www.ethereal.com/distribution/win32/development/gtk2
-or:
+or (like the GTK+1 libraries from the GTK+ for Win32 project):
http://www.gimp.org/~tml/gimp/win32/downloads.html
@@ -250,6 +229,26 @@ and optional:
Be sure to set GTK2_DIR in config.nmake correct, to be able to compile.
+Running your freshly compiled Ethereal
+--------------------------------------
+
+Make sure the glib and gtk DLL's are in your path or you use a directory
+where all required DLL's and the exe files reside.- i.e., that your
+path includes the directory (folder) or directories (folders) in which
+those DLLs are found - when you run Ethereal.
+
+Note the wiretap*.dll must be in your path as well and if wiretap is changed
+be sure to put the new one in your path.
+
+Plugins (gryphon.dll and mgcp.dll) can go in:
+ <Ethereal installation directory>\plugins\<version>
+
+Where <version> is the version number, without brackets. For example,
+if you have Ethereal 0.9.8 installed in the default location, plugins
+will reside in C:\Program Files\Ethereal\plugins\0.9.8
+
+Yes, the location of plugins needs to be more flexible.
+
Instructions for MS Visual C++
----------------------------
Modify the config.nmake file in the top directory of the Ethereal source