On Apr 3, 2012, at 4:33 PM, Jeff Morriss wrote:

> *My* intent was to revert back out my change to go back to what Joerg had 
> intended in r34356.  That revision says the intent was "to increase common 
> source code coverage".
> 
> I think I had also see some comments (r28285, for example) about 
> wanting/trying to get the AirPcap GUI working on Linux.  I don't know much 
> more than that since I don't have one of the devices to play with.  Joerg?
I understand the point of code coverage... However, as far as I know the stuff 
works only
on Windows. That's why we setup a test machine with Windows and test this with 
the AirPcap
devices Cace provided us. Having these devices helped a lot, but we only have 
them running
on Windows...

So Joerg: It makes sense to have the auto* stuff and the cmake stuff as much in 
line as
possible. But it would make sense to have the Airpcap stuff on by default on 
Windows,
and off by default on other platforms. We can leave support in for switching 
them on,
as this might help during development.

Best regards
Michael
> 
> Michael Tuexen wrote:
>> What is the reason to use Airpcap by default?
>> It is (as far as I know) only supported on Windows platforms, when having 
>> some
>> software installed. So why compile the stuff on non windows platforms?
>> Best regards
>> Michael
>> On Mar 27, 2012, at 4:37 AM, [email protected] wrote:
>>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=41790
>>> 
>>> User: morriss
>>> Date: 2012/03/26 07:37 PM
>>> 
>>> Log:
>>> Revert r37423: the intent of r34356 was to enable Airpcap by default, it 
>>> just
>>> didn't work as intended.
>>> 
>>> Then make it so we build with Airpcap by default.
>>> 
>>> This should hopefully be the end of 
>>> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4879
>>> 
>>> Directory: /trunk/
>>> Changes    Path            Action
>>> +7 -1      configure.in    Modified
>>> 
>>> ___________________________________________________________________________
>>> Sent via:    Wireshark-commits mailing list 
>>> <[email protected]>
>>> Archives:    http://www.wireshark.org/lists/wireshark-commits
>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
>>>            
>>> mailto:[email protected]?subject=unsubscribe
>>> 
> 
> 

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

Reply via email to