This isn't a new issue! I haven't been able to use the CYGWIN version
of Python to build WS, since I start with WS around March this year.
I have install the Win32 native version of Python (v2.3), no problem.
-Tim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECT
This issue started about three months ago when the python input files
were moved to the 'tools' directory & renamed. I believe it was Rev
18391 of .\dissectors\Makefile.nmake that first caused this issue, not
the version of Python.
Since the native Windows path specification includes "\" not "/",
I also have CYGWIN make package installed & can compile Wireshark with
MS VC 6. I don't have CYGWIN in my path or includes pointing to CYGWIN
when I open a COMMAND prompt to build.
-Tim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Graham Bl
What's your build environment details? It's hard to give relevant
answers without more background info!
For example:
1. Win32 with CYGWIN?
2. What version of MS VC++?
3. What version of Wireshark source, SVN (when updated last?) or 0.99.3
tar ball?
4. Were you able successfully build before chan
On Windows (2k/XP),
the link time is significant (1-2 minutes or at least it seems to be!).
Can anyone tell me which dissectors are required? I have been trying a few
tweaks to a dissector we are creating, the build to debug turn-around takes too
long.
In the past I've
just put up with
If you are using 0.99.1+ (maybe) or SVN version you may have this
problem!
This problem crept in several months ago when the python input file for
.\dissectors was renamed (maake-dissector-reg.py) and moved to a
sub-directory. This change was also made in the .\plugins\profinet &
sbus directorie
Top post Test!!!
I'd be interested if you can get Wireshark to build & debug in CYGWIN
only!!
-Tim
>
> A It makes it hard to understand the cause and effect.
> Q What's wrong with top-posting?
Not sure if you like or dislike top posting.
I'm using MS Outlook & the posts that I cc show up top
Have you explored the possibility of building using the recommended MSVC
6/ CYGWIN combination???
-Tim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, September 11, 2006 6:19 AM
> To: wireshark-dev@wireshark.o
Good deal.
I was a little surprised that you were having trouble, since I have seen
email from you about as long as I've been subscribed.
I've tried copying the CYGWIN setup from one machine to another (doesn't
work!). Had to reinstall CYGWIN!
-Tim
> -Original Message-
> From: [EMAIL P
I just did build based on source distribution 0.99.3 (retrieved today)!
I did find that the file \wireshark\airpcap.h is missing from the
distribution and causes the build to fail.
Before starting the first build, did you execute: "nmake
-fmakefile.nmake distclean" and "nmake -fmakefile.nmake set
Have you done the following:
Do you intend to build using MSVC & CYGWIN tools?
Was your Win32 build environment setup using the Developers Guide,
sections 2.3 & 4.6.2?
If you intended to use MSVC & CYGWIN tools, a command prompt [DOS
prompt] is the way to go!
Also ensure that you have run vcvars
What are you using as source (e.g. SVN tip or source distribution
0.99.3)? I usually build from SVN tip. However, I haven't applied
updates for couple months. Maybe I'll have time to update & do a clean
build.
-Tim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTE
Do you intend to build using MSVC & CYGWIN tools?
Was your Win32 build environment setup using the Developers Guide,
sections 2.3 & 4.6.2?
If you intended to use MSVC & CYGWIN tools, a command prompt [DOS
prompt] is the way to go!
I build using MSVC v6 & CYGWIN tools.
-Tim
> -Original M
Ben - Look at the follow http://wiki.wireshark.org/Development/Tips.
Look at the "Using MSVC++ for debugging" section. By default, the Win32
builds with the debug flag enabled.
GDB must be used in the CYGWIN environment (not easily
built!!).
-Tim
From: [EMAIL PROTECTED]
[ma
I use MSVC++ v6.0 & Cygwin. I recently spent better part of a week looking at
how to build entirely under Cygwin (just to support one person who has .net
2005). I finally concluded that it is way too much work. I opted to install
MS Virtual PC (now FREE) & setup an environment that can be mov
2006 5:34 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Using GNU Compiler & Project
> Debugger on Wiindows XP
>
> Cook, Timothy wrote:
> > Hi All - We recently received new PCs and upgraded from MS
> VC++ v6 to
> > .net 2005.
Hi All - We recently
received new PCs and upgraded from MS VC++ v6 to .net 2005. My question
is: Has anyone compiled Wireshark with .net 2005 (without changing the source!)
or Cygwin GNU compiler & Project debugger?
We intend to
distribute Wireshark package to customers for support
issue
My mistake, the distclean should be used after the verify_tools.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Cook, Timothy
> Sent: Wednesday, July 26, 2006 3:47 PM
> To: Developer support list for Wireshark
> Subjec
You may want to include: nmake -fmakefile.nmake distclean
as the first step. This will get rid of auto generated files that may
cause initial Win32 build to fail.
-Tim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Steve Grinwis
> Sent: Wednes
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Piercy
> Sent: Wednesday, July 12, 2006 7:27 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] making register.c - python problem
>
> Cook, Timothy wrote:
> > Using OS: Win XP SP2 Dev Env: MS VC 6 & CYGWIN
The following is from an email I sent to the DEV list without response.
This is how I fixed the problem locally.
Using OS: Win XP SP2 Dev Env: MS VC 6 & CYGWIN
The changes merged into .\epan\dissectors\Makefile.nmake Rev 18391 broke
my build. I believe there are several other makefile.nmake fil
Using OS: Win XP
SP2 Dev Env: MS VC 6 & CYGWIN
I'm fairly new to
building Wireshark & SVN usage.
The changes merged
into .\epan\dissectors\Makefile.nmake Rev 18391 broke my build. I believe
there are several other makefile.nmake files affected. I have been
able to continue building b
OS: WinXP w/
Cygwin
I've been coding a
new dissector using 0.99.1pre1 as the base, with no build
problems.
On June 23, I pulled the whole SVN
structure and built with no errors.
Today, I did an
SVN update, now I get the following error. I've checked my paths;
they match.
Help!!
23 matches
Mail list logo
