On Wed, Sep 29, 2010 at 01:37:07PM -0400, Andrew Suter wrote:
> Prior to this, no matter what I did I got a packet-ncp.c file that
> contained nothing. After doing this it contained code. I manually
> defined my PYTHON_VER and PYTHON_DIR in config.nmake and I think this
> causes a problem
I manged to resolve this issue by navigating to:
c:\wireshark-rim\epan\dissectors
and running:
c:\python26\python.exe "../../tools/ncp.py" -o packet-ncp.c
Prior to this, no matter what I did I got a packet-ncp.c file that
contained nothing. After doing this it contained code. I manu
Aladin Dajani wrote:
My guess: Something's wasn't right about the compile of packet-ncp222.c
(which indirectly contains the "unresolved external symbols" & etc).
(packet-ncp.inc included in packet-ncp.c has the symbols).
Were there any compile errors ?
Did you do a distclean before b
Hello,I followed the instructions to setup the build environment and to build
wireshark on Windows (XP + Visual Studio 2008).I am getting the following error:
Creating library libwireshark.lib and object
libwireshark.expdissectors.lib(packet-ncp.obj) : error LNK2001: unresolved
external symb
