From fae1db03269b748ae8d4eb23f87595f4a4cbcba7 Mon Sep 17 00:00:00 2001 From: Guy Harris Date: Thu, 3 Jan 2019 13:56:15 -0800 Subject: Slight fixup for where the capture code lives. The full explanation is a bit more complicated - we'd have to mention the dumpcap/*shark split, and the code on both sides of the split. Change-Id: I43f8fc3c589bdf900e20714b55a3b4f544879bc2 Reviewed-on: https://code.wireshark.org/review/31349 Reviewed-by: Guy Harris --- docbook/wsdg_src/WSDG_chapter_build_intro.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docbook/wsdg_src/WSDG_chapter_build_intro.asciidoc b/docbook/wsdg_src/WSDG_chapter_build_intro.asciidoc index 698f39cc41..43e1a4eddc 100644 --- a/docbook/wsdg_src/WSDG_chapter_build_intro.asciidoc +++ b/docbook/wsdg_src/WSDG_chapter_build_intro.asciidoc @@ -13,9 +13,10 @@ Wireshark consists of the following major parts: * Packet dissection - in the _/epan/dissectors_ and _/plugins/epan/{asterisk}_ directories -* File I/O - using Wireshark’s own wiretap library +* Capture file I/O - using Wireshark’s own wiretap library -* Capture - using the libpcap and Npcap libraries, in _/wiretap_ +* Capture - using the libpcap and Npcap libraries, in _dumpcap.c_ and +the _/capchild_ and _/caputils directories * User interface - using Qt and associated libraries -- cgit v1.2.3