/docbook/wsdg_src/WSDG_chapter_build_intro.adoc

https://gitlab.com/jvelando/wireshark · AsciiDoc · 52 lines · 32 code · 20 blank · 0 comment · 0 complexity · cf7a62ca034cd53ac253e09c92c40bb4 MD5 · raw file

  1. // WSDG Chapter Build Introduction
  2. [#ChapterBuildIntro]
  3. == Introduction
  4. [#ChCodeOverview]
  5. === Source overview
  6. Wireshark consists of the following major parts:
  7. * Packet dissection - in the _/epan/dissectors_ and
  8. _/plugins/epan/{asterisk}_ directories
  9. * Capture file I/O - using Wiresharks own wiretap library
  10. * Capture - using the libpcap and Npcap libraries, in _dumpcap.c_ and
  11. the _/capture_ directory
  12. * User interface - using Qt and associated libraries
  13. * Utilities - miscellaneous helper code
  14. * Help - using an external web browser and text output
  15. [#ChCodeStyle]
  16. === Coding Style
  17. The coding style guides for Wireshark can be found in the Portability
  18. section of the file _doc/README.developer_.
  19. [#ChCodeGLib]
  20. === The GLib library
  21. GLib is used as a basic platform abstraction library. It doesn't provide
  22. any direct GUI functionality.
  23. To quote the GLib Reference Manual:
  24. ____
  25. GLib provides the core application building blocks for libraries and
  26. applications written in C. It provides the core object system used in GNOME, the
  27. main loop implementation, and a large set of utility functions for strings and
  28. common data structures.
  29. ____
  30. GLib contains lots of useful things for platform independent development.
  31. See https://developer.gnome.org/glib/ and https://docs.gtk.org/glib/ for details about GLib.
  32. // End of WSDG Chapter Build Introduction