On 18 jul. 2011, at 15:15, Andreas wrote:
> Am 18.07.2011 10:12, schrieb Guy Harris:
>>
>> On Jul 18, 2011, at 1:02 AM, Helge Kruse wrote:
>>
>>> I use always C++ to write my custom dissectors. Did you surround the
>>> Wireshark #include with extern "C" like this?
>>
>> Perhaps Wireshark shou
Am 18.07.2011 15:22, schrieb sagar sg:
Okay, you mean to say we have to add the extern c { tfs.h } to the wireshark
code ?
No, it wouldn't help to solve your problem. You can add this guard in
your C++ project.
I just mentioned that Wireshark could be prepared to be used in a C++
project.
Okay, you mean to say we have to add the extern c { tfs.h } to the wireshark
code ?
On Mon, Jul 18, 2011 at 6:45 PM, Andreas wrote:
> Am 18.07.2011 10:12, schrieb Guy Harris:
>
>
>> On Jul 18, 2011, at 1:02 AM, Helge Kruse wrote:
>>
>> I use always C++ to write my custom dissectors. Did you sur
Am 18.07.2011 10:12, schrieb Guy Harris:
On Jul 18, 2011, at 1:02 AM, Helge Kruse wrote:
I use always C++ to write my custom dissectors. Did you surround the Wireshark #include
with extern "C" like this?
Perhaps Wireshark should surround the body of epan/tfs.h with that
Well, Wireshar
Am 18.07.2011 11:51, schrieb sagar sg:
How do u write makefile for that ? do u use gcc or g++ ? if u can paste a
sample makefile then that may help.
Honestly, I don't write any makefile, if I can avoid it.
I use the New-Project wizard of Visual Studio to create a DLL project,
add some files
How do u write makefile for that ? do u use gcc or g++ ? if u can paste a
sample makefile then that may help.
On Mon, Jul 18, 2011 at 1:32 PM, Helge Kruse wrote:
> Am 18.07.2011 07:16, schrieb sagar sg:
>
> Yes. My dissector code is in C++ which i am compiling independently and
>> using the req
On Jul 18, 2011, at 1:17 AM, sagar sg wrote:
> let me know, is there something need to be changed in code to compile it in
> linux. because in windows i was able to compile the same code success fully. ?
I have absolutely no idea, as I haven't seen the code. Perhaps there's
something that som
let me know, is there something need to be changed in code to compile it in
linux. because in windows i was able to compile the same code success fully.
?
On Mon, Jul 18, 2011 at 1:44 PM, Guy Harris wrote:
>
> On Jul 17, 2011, at 10:18 PM, sagar sg wrote:
>
> > Yes, I have
> >
> > #ifdef H
On Jul 17, 2011, at 10:18 PM, sagar sg wrote:
> Yes, I have
>
> #ifdef HAVE_CONFIG_H
># include "config.h"
>#endif
>
> But my code is in C++ and i am using gcc compiler. does this make any
> difference?
I wouldn't expect it to.
Could we see the code, please? You m
On Jul 18, 2011, at 1:02 AM, Helge Kruse wrote:
> I use always C++ to write my custom dissectors. Did you surround the
> Wireshark #include with extern "C" like this?
Perhaps Wireshark should surround the body of epan/tfs.h with that
Yes i did that..
On Mon, Jul 18, 2011 at 1:32 PM, Helge Kruse wrote:
> Am 18.07.2011 07:16, schrieb sagar sg:
>
> Yes. My dissector code is in C++ which i am compiling independently and
>> using the required libraries.
>>
>
> I use always C++ to write my custom dissectors. Did you surround the
>
Am 18.07.2011 07:16, schrieb sagar sg:
Yes. My dissector code is in C++ which i am compiling independently and
using the required libraries.
I use always C++ to write my custom dissectors. Did you surround the
Wireshark #include with extern "C" like this?
extern "C" {
#include
#includ
Yes. My dissector code is in C++ which i am compiling independently and
using the required libraries .
On Fri, Jul 15, 2011 at 8:42 PM, Stephen Fisher wrote:
> On Fri, Jul 15, 2011 at 08:34:48PM +0530, sagar sg wrote:
>
> >I am getting the following error during the compilation of the
> > d
Yes, I have
#ifdef HAVE_CONFIG_H
# include "config.h"
#endif
But my code is in C++ and i am using gcc compiler. does this make any
difference?
On Fri, Jul 15, 2011 at 8:38 PM, Jakub Zawadzki
wrote:
> Hi,
>
> On Fri, Jul 15, 2011 at 08:34:48PM +0530, sagar sg wrote:
> >I
Hi,
On Fri, Jul 15, 2011 at 08:34:48PM +0530, sagar sg wrote:
>I am getting the following error during the compilation of the dissector
> on linux platform, does anybody know the cause for this error and solution ??
> /wireshark/wireshark-1.4.7/epan/ftypes/ftypes.h:263: error: expected
> cons
On Fri, Jul 15, 2011 at 08:34:48PM +0530, sagar sg wrote:
>I am getting the following error during the compilation of the
> dissector on linux platform, does anybody know the cause for this
> error and solution ?? please reply.
> /wireshark/wireshark-1.4.7/epan/ftypes/ftypes.h:263: error: e
Hi,
I am getting the following error during the compilation of the dissector
on linux platform, does anybody know the cause for this error and solution
?? please reply.
/wireshark/wireshark-1.4.7/epan/ftypes/ftypes.h:263: error: expected
constructor, destructor, or type conversion before âu
/w
17 matches
Mail list logo
