osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Update to reflect the fact that you *HAVE* to have a Windows version of 

Flex in order to build Ethereal, as the UNIX version generates files
that unconditionally include <unistd.h> and thus don't build on Windows.

svn path=/trunk/; revision=7411
This commit is contained in:
Guy Harris 2003-04-07 22:39:25 +00:00
parent 43142cb77b
commit daa67ae37c
1 changed files with 24 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
README.win32
View File

@ -1,4 +1,4 @@
$Id: README.win32,v 1.44 2003/02/14 01:01:26 guy Exp $
$Id: README.win32,v 1.45 2003/04/07 22:39:25 guy Exp $
Installing Ethereal, Tethereal, and Editcap on Win32
====================================================
@ -191,10 +191,24 @@ In the ethereal directory, type "nmake -f makefile.nmake". It will
recurse into the subdirectories as appropriate.
Some generated source is created by traditionally "Unix-ish" tools.
If you are building from an official distribution, these files are
already generated, so you have nothing to worry about unless you
modify the source. If building from a CVS image, you'll need the tools
to generate C source. The "special" files and their requisite tools are:
already generated, although they were generated on a Unix-compatible
system. In most cases, the generated files can be used when building on
Windows, but the files listed below as being generated by Flex can be
used when building on Windows only when generated by a Windows version
of Flex, so you will need a Windows version of Flex to do a Windows
build. Those generated files are removed by the "cleanbld.bat" script,
to make sure that versions left over from a Unix build aren't used.
If you are building from a modified version of an official distribution,
and you modified any of the source files listed below, you will need the
tool(s) that generate output from those source files.
If building from a CVS image, you'll need all the tools to generate C
source.
The "special" files and their requisite tools are:
Source Output Tool
------ ------ ----
@ -230,15 +244,17 @@ script is one process. This matters a lot on Win32.
If you have a Unix system handy, you can first build on Unix to create
most of the source files that these tools make, then run the build on
Windows. That will avoid the need for these tools on your Windows
computer. (This won't work for the files in the "image" directory,
computer. This won't work for the files in the "image" directory,
however, as those aren't built on Unix - they're only for Windows
builds. It also won't work for the "config.h" files; whilst those are
built for Unix, they're specific to the platform on which you're
building, and the "config.h" files constructed for a Unix build will not
work with a Windows build.)
work with a Windows build. In addition, it won't work for the files
generated by Flex, as, for a Windows build, those have to be generated
by a Windows version of Flex.
If you don't have a Unix system handy, most of those tools are available for
Win32 systems as part of the Cygwin package:
Most of those tools are available for Win32 systems as part of the
Cygwin package:
http://sources.redhat.com/cygwin/