Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Ethereal: dev

Build ethereal under winXP

 

 

Ethereal dev RSS feed   Index | Next | Previous | View Threaded


Kai.Kang at nokia

May 29, 2006, 4:20 AM

Post #1 of 7 (1378 views)
Permalink
Build ethereal under winXP

Hi, all

I am newbie trying to use MSVC 6.0 to build ethereal under Windows XP,
In my cygwin shell, I tried:
------------------------------------------------------------------------
---------------------------------------------
$ nmake -f Makefile.nmake distclean

Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

rm -f gtk2.tmp/*.*
if exist gtk2.tmp rmdir gtk2.tmp
rm -f capture-wpcap.obj capture_wpcap_packet.obj
capture_errs.obj
capture-pcap-util.obj capture_stop_conditions.obj
capture_ui_utils.obj
cfile.obj clopts_common.obj conditions.obj
disabled_protos.obj
packet-range.obj print.obj ps.obj pcapio.obj
ringbuffer.obj
timestats.obj util.obj version_info.obj alert_box.obj
capture
.obj capture_info.obj capture_opts.obj capture_sync.obj
color_f
ilters.obj file.obj fileset.obj filters.obj
g711.obj merge
.obj proto_hier_stats.obj sync_pipe_write.obj summary.obj
tempfil
e.obj capture-wpcap.obj capture_wpcap_packet.obj capture_errs.obj
capture
-pcap-util.obj capture_stop_conditions.obj capture_ui_utils.obj
cfile.o
bj clopts_common.obj conditions.obj disabled_protos.obj
packet-
range.obj print.obj ps.obj pcapio.obj ringbuffer.obj
timesta
ts.obj util.obj version_info.obj tap-afpstat.obj
tap-ans
i_astat.obj tap-bootpstat.obj tap-dcerpcstat.obj
tap-funnel.obj
tap-gsm_astat.obj tap-h225counter.obj tap-h225rassrt.obj
tap-htt
pstat.obj tap-iostat.obj tap-iousers.obj
tap-mgcpstat.obj
tap-protocolinfo.obj tap-protohierstat.obj tap-rpcstat.obj
tap-rpc
progs.obj tap-sctpchunkstat.obj tap-sipstat.obj
tap-smbsids.obj
tap-smbstat.obj tap-stats_tree.obj tap-wspstat.obj
capture
_opts.obj capture_loop.obj tempfile.obj
tethereal-tap-register.obj tethereal.obj mkstemp.obj
strptime.obj e
thereal.exe ethereal-gtk2.exe tethereal.exe capinfos.exe editcap.exe
mergecap.e
xe text2pcap.exe randpkt.exe dumpcap.exe vc*.pdb capinfos.obj
editcap.obj merge
cap.obj text2pcap.obj getopt.obj text2pcap-scanner.obj
text2pcap-scanner.c rdps.
obj rdps.pdb rdps.exe rdps.ilk config.h ps.c AUTHORS-SHORT
AUTHORS-SHORT-FORMA
T dftest.obj dftest.exe randpkt.obj randpkt.ext dumpcap.obj
doxygen.cfg image
\ethereal.res image\libethereal.res image\tethereal.res
image\capinfos.res imag
e\editcap.res image\mergecap.res image\text2pcap.res image\wiretap.res
image\du
mpcap.res libethereal.dll wiretap-0.3.dll

cd asn1
NMAKE : fatal error U1077: 'cd' : return code '0x1'
Stop.

------------------------------------------------------------------------
----------------------------------------
What's the reason for this fatal error? And the advice to cope with it
is also very appreciated,


After directly download the source code(Ethereal-1.1.0-SVN-18188),
unpacked it, try configure it, the following problem encounted
------------------------------------------------------------------------
----------------------------------------
$ ./configure
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/bin/sh: /cygdrive/c/Documents: No such file or directory
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for a sed that does not truncate output... /usr/bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object
files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... file_magic ^x86 archive
import|
^x86 DLL
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line arguments... 8192
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -DDLL_EXPORT
checking if gcc PIC flag -DDLL_EXPORT works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking whether a program can dlopen itself... no
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking for g++ option to produce PIC... -DDLL_EXPORT
checking if g++ PIC flag -DDLL_EXPORT works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for g77 option to produce PIC... -DDLL_EXPORT
checking if g77 PIC flag -DDLL_EXPORT works... yes
checking if g77 static flag -static works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking for bison... bison -y
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for perl... /usr/bin/perl
checking for pod2man... /usr/bin/pod2man
checking for pod2html... /usr/bin/pod2html
checking for htmlview... no
checking for flex... /usr/bin/flex
checking for python... /usr/bin/python
checking for doxygen... /usr/bin/doxygen
checking for doxygen... yes
checking for libgnutls-config... /usr/bin/libgnutls-config
checking for libgnutls - version >= 1.0.0... yes
gnuTLS found, enabling ssl decryption
checking for xsltproc... /usr/bin/xsltproc
checking for xsltproc... yes
checking for xmllint... /usr/bin/xmllint
checking for xmllint... yes
checking for fop... no
checking for fop... no
checking for hhc.exe... no
checking for hhc.exe... no
checking for pkgproto... no
checking for pkgmk... no
checking for pkgtrans... no
checking for rpm... yes
checking to see if we can redefine _topdir... yes
checking to see if we can add '-Wall -W ' to CFLAGS... yes
checking for platform-specific compiler flags... CygWin GCC - added
-no-undefine
d to LDFLAGS
checking whether to use /usr/local for headers and libraries... yes
checking for GNU sed as first sed in PATH... yes
checking if profile builds must be generated... no
checking for pkg-config... /usr/bin/pkg-config
checking for GTK+ - version >= 2.0.0... yes (version 2.6.10)
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for GLIB - version >= 2.0.0... yes (version 2.6.6)
checking whether GLib supports loadable modules... yes
checking for inttypes.h... (cached) yes
checking whether inttypes.h defines the PRI[doxu]64 macros... yes
checking for gethostbyname... yes
checking for connect... yes
checking whether to use libpcap for packet capture... yes
checking for extraneous pcap header directories... not found
checking pcap.h usability... no
checking pcap.h presence... no
checking for pcap.h... no
configure: error: Header file pcap.h not found; if you installed libpcap
from source, did you also do "make install-incl", and if you installed a
binary package of libpcap, is there also a developer's package of
libpcap,
and did you also install that package?

------------------------------------------------------------------------
--------------------------------------
Should I install Libpcap separately?


And then I try to install libpcap-0.9.4, unfortunately, error
encountered again as
------------------------------------------------------------------------
--------------------------------------
$ ./configure
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for gcc... gcc
checking for C compiler default output... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking gcc version... 3
checking for inline... inline
checking for __attribute__... yes
checking for u_int8_t using gcc... yes
checking for u_int16_t using gcc... yes
checking for u_int32_t using gcc... yes
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/ioccom.h usability... no
checking sys/ioccom.h presence... no
checking for sys/ioccom.h... no
checking sys/sockio.h usability... no
checking sys/sockio.h presence... no
checking for sys/sockio.h... no
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for netinet/if_ether.h... no
configure: Rechecking with some additional includes
checking for netinet/if_ether.h... no
checking for ANSI ioctl definitions... no
configure: error: see the INSTALL for more info

------------------------------------------------------------------------
-------------------------
What should do under current circumstance? Any suggestion is very
appreciated. Many thanks in advance for your valuable time and
considerations!!

Br
Kai Kang
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev


wmeier at newsguy

May 29, 2006, 5:59 AM

Post #2 of 7 (1299 views)
Permalink
Re: Build ethereal under winXP [In reply to]

> Hi, all
>
> I am newbie trying to use MSVC 6.0 to build ethereal under Windows XP,
> In my cygwin shell, I tried:
> ------------------------------------------------------------------------
> ---------------------------------------------
> $ nmake -f Makefile.nmake distclean
>

<munch>

>
>
> After directly download the source code(Ethereal-1.1.0-SVN-18188),
> unpacked it, try configure it, the following problem encounted
> ------------------------------------------------------------------------
> ----------------------------------------
> $ ./configure
> checking build system type... i686-pc-cygwin

<munch>


I believe the short answer is that the standard way to build Ethereal under
windows does *not* involve the use of configure & etc.

In essence:

1. Install basic cygwin (... bash & etc);

2. Download and unpack Ethereal source;

3. Look at (and change if desired) the config.nmake in the top-level Ethereal
directory to specify certain things such the location of cygwin (CYGWIN_PATH)
and the location to store various required library stuff (ETHEREAL_LIBS).

4. Determine/verify the presence of the required cygwin tools using

nmake -f makefile.nmake verify_tools

(Download additional cygwin stuff as required)

5. Download the various required libraries by using

nmake -f makefile.nmake setup


6. Make ethereal

nmake -f makefile.nmake dist-clean

nmake -f makefile.nmake all


I've undoubtely left something out; the details can be found in the
developer's guide available at:

http://www.ethereal.com/docs/


Bill Meier





_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev


graham.bloice at trihedral

May 29, 2006, 6:09 AM

Post #3 of 7 (1306 views)
Permalink
RE: Build ethereal under winXP [In reply to]

> -----Original Message-----
> From: ethereal-dev-bounces [at] ethereal
> [mailto:ethereal-dev-bounces [at] ethereal]On Behalf Of Bill Meier
> Sent: 29 May 2006 14:00
> To: ethereal-dev [at] ethereal
> Cc: Kai.Kang [at] nokia
> Subject: Re: [Ethereal-dev] Build ethereal under winXP
>
>
>
> > Hi, all
> >
> > I am newbie trying to use MSVC 6.0 to build ethereal under Windows XP,
> > In my cygwin shell, I tried:
> > ------------------------------------------------------------------------
> > ---------------------------------------------
> > $ nmake -f Makefile.nmake distclean
> >
>
> <munch>
>
> >
> >
> > After directly download the source code(Ethereal-1.1.0-SVN-18188),
> > unpacked it, try configure it, the following problem encounted
> > ------------------------------------------------------------------------
> > ----------------------------------------
> > $ ./configure
> > checking build system type... i686-pc-cygwin
>
> <munch>
>
>
> I believe the short answer is that the standard way to build
> Ethereal under
> windows does *not* involve the use of configure & etc.
>
> In essence:
>
> 1. Install basic cygwin (... bash & etc);
>
> 2. Download and unpack Ethereal source;
>
> 3. Look at (and change if desired) the config.nmake in the
> top-level Ethereal
> directory to specify certain things such the location of cygwin
> (CYGWIN_PATH)
> and the location to store various required library stuff (ETHEREAL_LIBS).
>

3.a In the same cmd prompt you will be using for subsequent operations run
vcvars32.bat. This is normally located in the MSVC\VC98\Bin directory.
This ensures that the paths are correctly set for the MS toolchain.

> 4. Determine/verify the presence of the required cygwin tools using
>
> nmake -f makefile.nmake verify_tools
>
> (Download additional cygwin stuff as required)
>
> 5. Download the various required libraries by using
>
> nmake -f makefile.nmake setup
>
>
> 6. Make ethereal
>
> nmake -f makefile.nmake dist-clean
>
> nmake -f makefile.nmake all
>
>
> I've undoubtely left something out; the details can be found in the
> developer's guide available at:
>
> http://www.ethereal.com/docs/
>
>
> Bill Meier
>
>
>
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev [at] ethereal
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev


wmeier at newsguy

May 29, 2006, 6:26 AM

Post #4 of 7 (1316 views)
Permalink
RE: Build ethereal under winXP [In reply to]

Fixed typo: It's distclean not dist-clean when making Ethereal





> > -----Original Message-----
> > From: ethereal-dev-bounces [at] ethereal
> > [mailto:ethereal-dev-bounces [at] ethereal]On Behalf Of Bill Meier
> > Sent: 29 May 2006 14:00
> > To: ethereal-dev [at] ethereal
> > Cc: Kai.Kang [at] nokia
> > Subject: Re: [Ethereal-dev] Build ethereal under winXP
> >
> >
> >
> > > Hi, all
> > >
> > > I am newbie trying to use MSVC 6.0 to build ethereal under Windows XP,
> > > In my cygwin shell, I tried:
> > > ------------------------------------------------------------------------
> > > ---------------------------------------------
> > > $ nmake -f Makefile.nmake distclean
> > >
> >
> > <munch>
> >
> > >
> > >
> > > After directly download the source code(Ethereal-1.1.0-SVN-18188),
> > > unpacked it, try configure it, the following problem encounted
> > > ------------------------------------------------------------------------
> > > ----------------------------------------
> > > $ ./configure
> > > checking build system type... i686-pc-cygwin
> >
> > <munch>
> >
> >
> > I believe the short answer is that the standard way to build
> > Ethereal under
> > windows does *not* involve the use of configure & etc.
> >
> > In essence:
> >
> > 1. Install basic cygwin (... bash & etc);
> >
> > 2. Download and unpack Ethereal source;
> >
> > 3. Look at (and change if desired) the config.nmake in the
> > top-level Ethereal
> > directory to specify certain things such the location of cygwin
> > (CYGWIN_PATH)
> > and the location to store various required library stuff (ETHEREAL_LIBS).
> >
>
> 3.a In the same cmd prompt you will be using for subsequent operations run
> vcvars32.bat. This is normally located in the MSVC\VC98\Bin directory.
> This ensures that the paths are correctly set for the MS toolchain.
>
> > 4. Determine/verify the presence of the required cygwin tools using
> >
> > nmake -f makefile.nmake verify_tools
> >
> > (Download additional cygwin stuff as required)
> >
> > 5. Download the various required libraries by using
> >
> > nmake -f makefile.nmake setup
> >
> >
> > 6. Make ethereal
> >
nmake -f makefile.nmake distclean
> >
> > nmake -f makefile.nmake all
> >
> >
> > I've undoubtely left something out; the details can be found in the
> > developer's guide available at:
> >
> > http://www.ethereal.com/docs/
> >
> >
> > Bill Meier
> >
> >
> >
> >
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > Ethereal-dev [at] ethereal
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev [at] ethereal
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>



_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev


dave.ramsey at blueyonder

May 29, 2006, 2:25 PM

Post #5 of 7 (1322 views)
Permalink
RE: Build ethereal under winXP [In reply to]

If it makes a difference, you should execute the build command from a
windows command (cmd) prompt, not Cygwin shell ... From the same command
prompt ensure you have also run VCVARS32

GL
Dave


-----Original Message-----
From: ethereal-dev-bounces [at] ethereal
[mailto:ethereal-dev-bounces [at] ethereal] On Behalf Of Kai.Kang [at] nokia
Sent: 29 May 2006 12:21
To: ethereal-dev [at] ethereal
Subject: [Ethereal-dev] Build ethereal under winXP

Hi, all

I am newbie trying to use MSVC 6.0 to build ethereal under Windows XP,
In my cygwin shell, I tried:
<Snipped>



_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev


ramans at blr

May 29, 2006, 3:35 PM

Post #6 of 7 (1321 views)
Permalink
Re: Build ethereal under winXP [In reply to]

1. unzip tar ball.
2. install cugwin with necessary components
3. install msvc++
4. set environment vairables by vcvars32
5. set correct path.( by PATH=
6. copy win32.mak into witetap,epan, pluggins/mate, pluggins/stats_tree in
case u have a win32.mak errror
NOTE : following on command prompt not on cygwin prompt
7. nmake -f makefile.nmake distclean
8. nmake -f makefile.nmake verify_tools
9. nmake -f makefile.nmake setup
(if ur HTTP proxy is set then it will automatically download required
libraries else u need to download it mannually in correct path
(config.nmake) path)
10. sometimes (like in my case) need to give -I option (i.e. include path
in cl.exe b'cos it was not taking automatically from environment vairable)
with cl so in order to do so, changes in makefile.nmake. (most of time it is
not required)
11. nmake -f makefile.nmake
12. copy libraries into ethereal main folder. from all downloaded & from
wiretap & epan.
13. run ethereal, build new dissectors & contribute to this mailing list.

----- Original Message -----
From: "Dave Ramsey" <dave.ramsey [at] blueyonder>
To: "'Ethereal development'" <ethereal-dev [at] ethereal>
Sent: 2006 May 30 2:55 AM
Subject: RE: [Ethereal-dev] Build ethereal under winXP


>
> If it makes a difference, you should execute the build command from a
> windows command (cmd) prompt, not Cygwin shell ... From the same command
> prompt ensure you have also run VCVARS32
>
> GL
> Dave
>
>
> -----Original Message-----
> From: ethereal-dev-bounces [at] ethereal
> [mailto:ethereal-dev-bounces [at] ethereal] On Behalf Of Kai.Kang [at] nokia
> Sent: 29 May 2006 12:21
> To: ethereal-dev [at] ethereal
> Subject: [Ethereal-dev] Build ethereal under winXP
>
> Hi, all
>
> I am newbie trying to use MSVC 6.0 to build ethereal under Windows XP,
> In my cygwin shell, I tried:
> <Snipped>
>
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev [at] ethereal
> http://www.ethereal.com/mailman/listinfo/ethereal-dev

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev


graham.bloice at trihedral

May 30, 2006, 1:21 AM

Post #7 of 7 (1323 views)
Permalink
RE: Build ethereal under winXP [In reply to]

> -----Original Message-----
> From: ethereal-dev-bounces [at] ethereal
> [mailto:ethereal-dev-bounces [at] ethereal]On Behalf Of Raman Singla
> Sent: 29 May 2006 23:36
> To: Ethereal development
> Subject: Re: [Ethereal-dev] Build ethereal under winXP
>
>
> 1. unzip tar ball.
> 2. install cugwin with necessary components
> 3. install msvc++
> 4. set environment vairables by vcvars32

NB. This should be done EVERY time you open a new command prompt for
ethereal dev work. vcvars32 only affects the environment vars for the
current command prompt. You can of course make the changes permanent by
updating the environment vars in the Advanced tab of the System Properties
dialog (Windows key + Break).

> 5. set correct path.( by PATH=

Personally I have never needed to do this. See note above.

> 6. copy win32.mak into witetap,epan, pluggins/mate,
> pluggins/stats_tree in
> case u have a win32.mak errror

Personally I have never needed to do this, see note above.

> NOTE : following on command prompt not on cygwin prompt
> 7. nmake -f makefile.nmake distclean
> 8. nmake -f makefile.nmake verify_tools
> 9. nmake -f makefile.nmake setup
> (if ur HTTP proxy is set then it will automatically download required
> libraries else u need to download it mannually in correct path
> (config.nmake) path)
> 10. sometimes (like in my case) need to give -I option (i.e. include path
> in cl.exe b'cos it was not taking automatically from environment
> vairable)
> with cl so in order to do so, changes in makefile.nmake. (most of
> time it is
> not required)

Personally I have never needed to do this, see note above.

> 11. nmake -f makefile.nmake
> 12. copy libraries into ethereal main folder. from all downloaded & from
> wiretap & epan.
> 13. run ethereal, build new dissectors & contribute to this mailing list.
>

<SNIPPED>

Regards,

Graham

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev [at] ethereal
http://www.ethereal.com/mailman/listinfo/ethereal-dev

Ethereal dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.