Wireshark-bugs: [Wireshark-bugs] [Bug 11367] "make install" with CMake installs incomplete app b
Comment # 11
on bug 11367
from Gerald Combs
(In reply to Jörg Mayer from comment #10)
> Ah, OK, so i missed answering that point. Yes, I changed that immediately
> after reading about it and since that time my install process works.
> How do I run wireshark from that bundle from the command line including
> options (e.g. Wireshark -v for bugreports)?
The executable in Contents/MacOS should run fine from the command line:
----
$ ./Wireshark.app/Contents/MacOS/Wireshark -v
Wireshark 2.1.0 (v2.1.0rc0-97-g14085e0 from master)
Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.44.1, without SMI, with c-ares 1.10.0, with Lua 5.2,
with GnuTLS 3.3.10, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with
QtMultimedia, without AirPcap.
Running on Mac OS X 10.9.5, build 13F1112 (Darwin 13.4.0), with locale C, with
libpcap version 1.3.0 - Apple version 41, with libz 1.2.5, with GnuTLS 3.3.10,
with Gcrypt 1.6.2.
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (with SSE4.2)
Built using clang 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57).
----
The "wireshark" in ${CMAKE_BINARY_DIR}/run is a simple wrapper script that
passes the application bundle and any arguments to the "open" command. It might
make more sense to run the application directly if we have any arguments since
you're more likely to expect output in that case.
You are receiving this mail because:
- You are watching all bug changes.
