Re: [Wireshark-dev] QT DLLs missing from build environment

I did the following: *Deleted the QT5.5.1 directory *Installed Qt5.6.1 *Deleted my wsbuild64 directory content *Ran the cmake build prep step *Opened the Wireshark.sln in VS 2013 *Set Wireshark as the Startup Project *Ran a Build for

Re: [Wireshark-dev] Correct way to add bytes to tree

Hi all, Thanks for the prompt answers. I have ended up adding the value as a sub-element. So I don't need to do what I specified above anymore. Patch here! https://code.wireshark.org/review/#/c/19458/ Thanks, Juanjo Martin On Wed, Dec 28, 2016 at 8:46 PM, Alexis La Goutte

Re: [Wireshark-dev] Linking on OSX Sierra

I wonder if you all build using clang? I use gcc6 (qt5 version 5.7.0, all installed using home brew), and get the below compilation issue on Sierra (and likely since my recent upgrade to Sierra). Any ideas? Thanks! cd /Users/itisntme6/data/wireshark/wireshark/build/wsutil &&

Re: [Wireshark-dev] Linking on OSX Sierra

Hi, It is a issue with CoreFoundation Framework (don't build with gcc6) http://stackoverflow.com/a/41101276 Cheers On Thu, Dec 29, 2016 at 11:18 AM, Not Me wrote: > I wonder if you all build using clang? > > I use gcc6 (qt5 version 5.7.0, all installed using home brew),

Re: [Wireshark-dev] asn2wrs again

Hi Eliot, 2016-12-24 12:52 GMT+01:00 Eliot Lear : > Sorry to whine about this, but I'm struggling with the documentation a > bit. I'm trying to understand what is necessary to cause wireshark to > interpret a new OID in a certificate (a certificate extension- it's just

Re: [Wireshark-dev] asn2wrs again

Thanks for your comment. I got it working. I'll make a pull request in a few days' time. Eliot On 12/29/16 5:54 PM, Pascal Quantin wrote: > Hi Eliot, > > 2016-12-24 12:52 GMT+01:00 Eliot Lear >: > > Sorry to whine about this,