Comment # 2
on bug 11355
from Guy Harris
Yes, it appears it would be those bugs; building with Qt 5.5.0 seems to have
fixed the problem.
According to
http://doc.qt.io/qt-5/osx.html
"OS X Versions
OS X 10.7 "Lion" and 10.8 "Mountain Lion" are considered reference
configurations, meaning they are tested by a continuous integration (CI)
system. Qt 5 applications may be deployed to Mac OS X versions 10.6 "Snow
Leopard", but support is limited."
I don't know whether this applies to Qt 5.5 or not; hopefully, it does.
The Qt developers have made the "broken .pc files" probably *worse*, not
*better*, in Qt 5.5 (or maybe they did so in 5.4), with some superfluous
quoting of -framework arguments. I'll update macosx-setup.sh to handle that.
They also decided to make the "install name" of the Qt frameworks start with
@rpath, which means that:
1) in order to run a Qt Wireshark you've built with autotools from the
command line in the build directory, you have to precede it with
DYLD_FALLBACK_FRAMEWORK_PATH=$HOME/Qt5.5.0/5.5/clang_64/lib
or whatever is appropriate for the path in which Qt is installed;
2) this may require changes to the process of building the app bundle.
You are receiving this mail because:
- You are watching all bug changes.