Minor Development Guide updates
Corrected info about paths to built executable. Cross referenced empty debugger sections to the section with info. Change-Id: I4366825990f1a5286c7292c9f00e540160c1b5d0 Reviewed-on: https://code.wireshark.org/review/6520 Reviewed-by: Michael Mann <mmann78@netscape.net> Reviewed-by: Graham Bloice <graham.bloice@trihedral.com>
This commit is contained in:
parent
0ee179c8c6
commit
36aca292fb
|
@ -171,6 +171,8 @@ so it shows a version number for:
|
||||||
// Only used by win-setup.sh
|
// Only used by win-setup.sh
|
||||||
* Web/wget
|
* Web/wget
|
||||||
|
|
||||||
|
* asciidoc
|
||||||
|
|
||||||
// Also need: bash/sh, sed
|
// Also need: bash/sh, sed
|
||||||
|
|
||||||
You might also have to install
|
You might also have to install
|
||||||
|
@ -469,9 +471,9 @@ to build Wireshark.
|
||||||
|
|
||||||
. Wait for Wireshark to compile. This will take a while, and there will be a lot of text output in the command prompt window
|
. Wait for Wireshark to compile. This will take a while, and there will be a lot of text output in the command prompt window
|
||||||
|
|
||||||
. Run `C:\Development\wireshark\wireshark-qt-release\Wireshark.exe` and make sure it starts.
|
. For the QT version run `C:\Development\wireshark\wireshark-qt-release\Wireshark.exe` and make sure it starts.
|
||||||
|
|
||||||
//. Run `C:wiresharkwireshark-gtk2wireshark-gtk.exe` and make sure it starts.
|
. For the older GTK version run `C:\Development\wireshark\wireshark-gtk2\Wireshark-gtk.exe`.
|
||||||
|
|
||||||
. Open 'Help -> About'. If it shows your "private" program
|
. Open 'Help -> About'. If it shows your "private" program
|
||||||
version, e.g.: Version wireshark-major-minor-version:[].x-myprotocol123
|
version, e.g.: Version wireshark-major-minor-version:[].x-myprotocol123
|
||||||
|
@ -483,12 +485,8 @@ the sources and make "all" again
|
||||||
|
|
||||||
==== Debug Environment Setup
|
==== Debug Environment Setup
|
||||||
|
|
||||||
****
|
You can debug using the Visual Studio Debugger or WinDbg. See the section
|
||||||
Unfortunately this section hasn't been written. You should be able
|
on using the <<ChToolsDebugger, Debugger Tools>>.
|
||||||
to use the Visual Studio debugger to attach to a running executable.
|
|
||||||
Alternately, if you are building QtShark with Qt Creator, you can
|
|
||||||
launch QtShark in the debugger included with that IDE.
|
|
||||||
****
|
|
||||||
|
|
||||||
==== Optional: Create User's and Developer's Guide
|
==== Optional: Create User's and Developer's Guide
|
||||||
|
|
||||||
|
|
|
@ -469,8 +469,12 @@ be informative when things don't work as expected.
|
||||||
==== Win32 native
|
==== Win32 native
|
||||||
|
|
||||||
During the build all relevant program files are collected in a subdirectory
|
During the build all relevant program files are collected in a subdirectory
|
||||||
'wireshark-gtk2'. You can run the program from there by
|
'wireshark-qt-release'. You can run the program from there by
|
||||||
launching the wireshark.exe executable.
|
launching the Wireshark.exe executable.
|
||||||
|
|
||||||
|
The older GTK based version is also available in the 'wireshark-gtk'
|
||||||
|
subdirectory. You can run the program from there by launching the
|
||||||
|
Wireshark-gtk.exe executable.
|
||||||
|
|
||||||
|
|
||||||
[[ChSrcDebug]]
|
[[ChSrcDebug]]
|
||||||
|
@ -509,9 +513,8 @@ See http://library.gnome.org/devel/glib/stable/glib-running.html[]
|
||||||
|
|
||||||
==== Win32 native
|
==== Win32 native
|
||||||
|
|
||||||
****
|
You can debug using the Visual Studio Debugger or WinDbg. See the section
|
||||||
To be written
|
on using the <<ChToolsDebugger, Debugger Tools>>.
|
||||||
****
|
|
||||||
|
|
||||||
[[ChSrcChange]]
|
[[ChSrcChange]]
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue