Wireshark-dev: Re: [Wireshark-dev] making register.c - python problem
From: "Cook, Timothy" <[email protected]>
Date: Wed, 12 Jul 2006 08:44:48 -0400
No. I'm Python 2.3.5 (Windows Native).

I've also tried the CYGWIN Python, however, the env call that's suppose
to return the path fails.  I haven't had a lot of time to debug the
problem in detail.

-Tim

> -----Original Message-----
> From: [email protected] 
> [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
> 
> Out of interest, are you using Windows Python 2.4 ? I 
> reported the same when I moved to 2.4 (but the "official" 
> Windows native (i.e. non-cygwin) Python for wireshark is still 2.3) ?
> 
> >  I have been able to continue building by replacing line:
> > 
> >  @$(PYTHON) ../../tools/make-dissector-reg.py . dissectors
> > $(DISSECTOR_SRC)
> > 
> > with
> > 
> >  @$(PYTHON) "../../tools/make-dissector-reg.py" . dissectors
> > $(DISSECTOR_SRC)
> 
> My version of a fix was to replace all "/" with "\" for the 
> native Windows (i.e. non-cygwin) tool usage in nmake-files.
> 
> Neil
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
> 
> ______________________________________________________________
> _______________
> Scanned by IBM Email Security Management Services powered by 
> MessageLabs. For more information please visit 
> http://www.ers.ibm.com 
> ______________________________________________________________
> _______________
>