On Jul 22, 2015, at 8:20 PM, Luke Mewburn <luke@xxxxxxxxxxx> wrote:
> I suspect that this Qt bug (QTBUG-34160) may not be easily worked-around
> within Wireshark without radical menu reorganisation.
I'm not sure how radical
https://code.wireshark.org/review/#/c/9760/
is, but do the issues from bug 10890 remain after that change?
As for Copy Bytes, that's just not implemented yet, according to Alexis La Goutte:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10890#c12
> Details:
>
> I tried building against 5.5.0 from qt.io
> (qt-opensource-mac-x64-clang-5.5.0.dmg)
> after disabling the homebrew version in /usr/local,
> but it's been a bit of a hassle to get it to build and link.
Any hassle other than having to fix the .pc files?
> I think the pkg-config .pc files that are shipped with the qt.io are
> broken (that's an Qt5.5.0 upstream problem).
To be particular, it's problems (plural) QTBUG-35256:
https://bugreports.qt.io/browse/QTBUG-35256
which predates Qt 5.5.0 and QTBUG-47162:
https://bugreports.qt.io/browse/QTBUG-47162
which is new in 5.5.0.
> I had to manually edit Makefile and ui/qt/Makefile and
> add -F and various -I to CXXFLAGS, and fix incorrectly escaped
> -framework\ FOO (remove the \ between "-framework" and the argument).
The macosx-setup.sh script not only downloads the Qt image and runs its installer, it runs an editing script afterwards that fixes those problem.
If you're building Wireshark from source on OS X, the best way to get the relevant libraries installed is with that script, which will do the downloading, patching as necessary, compiling if it's a source rather than a binary installation, and installation for you.