Wireshark-dev: Re: [Wireshark-dev] Follow up to making register.c - python problem - patch
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 "/",
correct the slashes.
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Ulf Lamping
> Sent: Thursday, October 26, 2006 4:34 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Follow up to making register.c -
> python problem - patch
>
> Neil Piercy wrote:
> > Any chance of getting this patch applied ? I've updated the
> patch in
> > bugzilla (#1157, not the typo'ed number below) to the latest SVN.
> >
> >
> Hi!
>
> Yes, the current cygwin python binding has some problems,
> I've installed it and compile without your changes! I just
> don't really understand why???
>
> I've started to put the string name in brackets "../../xy.py"
> in one of the nmake files some days ago, instead of replacing
> the slashes by backslashes as you did - which seems to both
> be working with native python.
>
> Do you know of any drawbacks of either solutions?
>
> I still don't have a good idea what the right solution to
> this problem really is - and don't want to change a lot of
> places just to notice that this raises other problems :-)
>
> Regards, ULFL
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> 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
> ______________________________________________________________
> _______________
>
