Re: Build problem in private branch

[Anders Broman <anders.broman () ericsson com>]

Checking out a new working copy of the internal branch seems to have fixed it...still weird as I think I cleaned 
everything.
Regards
Anders

-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Anders Broman
Sent: den 7 juli 2013 23:04
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Build problem in private branch



-----Original Message-----
From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Guy Harris
Sent: den 7 juli 2013 22:58
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Build problem in private branch


On Jul 7, 2013, at 1:44 PM, Anders Broman <anders.broman () ericsson com> wrote:

> This have been driving me nuts today, I can build Wireshark from trunk 
> but not my private tree which is made by copying Wireshark/trunk files into a separate svn dir Masking out some files.
> capture_dlg.c(1279) : error C2220: warning treated as error - no 
> 'object' file generated
> capture_dlg.c(1279) : warning C4020: 'capture_get_if_capabilities' : 
> too many actual parameters
> capture_dlg.c(1410) : warning C4020: 'capture_interface_list' : too 
> many actualparameters
> capture_dlg.c(5301) : warning C4020: 'capture_start' : too many actual 
> parameters

In your private branch, are capture.h and capture_ifinfo.h at rev 50188 or greater?  Rev 50188 added a parameter to 
capture_start(), capture_get_if_capabilities(), and capture_interface_list():

Yes it is, but somehow that change does not seem to be picked up, or? Which is weird as I have rebuilt from scratch 
many times...ARGH

        ------------------------------------------------------------------------
        r50188 | lego | 2013-06-27 10:10:50 -0700 (Thu, 27 Jun 2013) | 8 lines

        get main_window_update out of the way... pass an update_cb to the capture_sync stuff
        ... as per the XXX comment removed from tshark.c this was a mess to keep the linker
        happy... I couldn't!

        I did this without even understanding whether calling main_window_update was realy
        necessary in most cases. I guess nothing or more specific update cbs would be best.

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