Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] mix of c and C++

From: sagar sg <sagu072@xxxxxxxxx>
Date: Mon, 18 Jul 2011 20:15:39 +0530
compiler i am using is  g++
parameters -   -fPIC
root/wireshark/wireshark-1.4.7/epan/tfs.h:56: error: expected constructor, destructor, or type conversion before âconstâ
error is in the file given above .. its not showing in the dissector code.

On Mon, Jul 18, 2011 at 6:53 PM, Helge Kruse <Helge.Kruse-nospam@xxxxxxx> wrote:
Am 18.07.2011 11:24, schrieb sagar sg:

hello,
        My Dissector is in C++ and internally uses wireshark libraries ( eg:
epan ) , Is there any way to wrote makefile such that we can mix the gcc and
g++ compilers for particular type of code to be compiled with corresponding
compiler ??

Thanks
Sagar G



This mix is not a Wireshark problem, but a general tools question.

The makefile defines, which tools shall be started in a specific order to generate the result. This can be a program if you use a C/C++ compiler and a linker or anything else, e.g. when compiling beautiful PDF files from LaTex source.

When you want to address C/C++ mixed code you just need to discuss how to write the source code and how to use the compilers. Regarding your problem to compile something that includes tfs.h you should send following:

- the name of the compiler that is actually started (gcc,g++)
- the exact list of parameters passed to the compiler
- the exact error message, (copy&paste is your friend)
- an excerpt of your source file with all lines including the line that causes the error.

Of course it's more convenient to send the complete source file instead of the excerpt.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
           mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe