[Roland Knall <rknall@xxxxxxxxx>]

Hi

Try not to run cmake but instead run cmake-gui, using the same parameters. Additionally, it is useful to create a separate build directory. therefore, build-files wil not clutter up the src space.

So, checkout wireshark, make a goto wireshark, create a directory named "build" cd into it and call "cmake-gui .."

After the first configure run, you can set the paths in the gui, and then run configure and  generate again.

Afterwards you can just run "make" or eclipse, depending on the project you created.

regards, 

Roland

On Wed, Nov 7, 2012 at 1:22 PM, Akos Vandra <axos88@xxxxxxxxx> wrote:

Hi guys!

I am new to cmake, and I am unable to compile Wireshark for Qt.

Can someone please write a step-by-step guide on what commands I have to issue in order to build it?

This is what I wanted to try:

edit CMakeOptions is trunk/ and set GTK to OFF, QT to ON.

"cmake ."

"make -j 10"

My output for cmake:

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.

Please set them or make sure they are set and tested correctly in the CMake files:

PCAP_LIBRARY

    linked by target "dftest" in directory /home/akos/projects/c/wireshark/wireshark_original/trunk

    linked by target "qtshark" in directory /home/akos/projects/c/wireshark/wireshark_original/trunk

    linked by target "randpkt" in directory /home/akos/projects/c/wireshark/wireshark_original/trunk

    linked by target "tshark" in directory /home/akos/projects/c/wireshark/wireshark_original/trunk

    linked by target "epan" in directory /home/akos/projects/c/wireshark/wireshark_original/trunk/epan

Problem is that I use a custom libpcap, but don't know how I should tell cmake that.

With ./configure I just added a parameter (--with-pcap="path to custom pcap library", or something similar), and it was fine, but with cmake, I have no idea how to do it. Tried adding some lines to cmakeoptions, but neither of them worked.

Regards,

  Ákos Vandra

___________________________________________________________________________
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@xxxxxxxxxxxxx?subject=unsubscribe