Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Sun, 10 Jun 2007 09:44:08 -0700

Guy Harris wrote:

init_progfile_dir() should probably be called regardless of whether we're building with plugin support or not, given, for example, the WIRESHARK_RUN_FROM_BUILD_DIRECTORY environment variable.

...and init_report_err() should probably always be called as well.

Perhaps init_plugins() should be a stub routine that does nothing if --with-plugins=no is specified? And perhaps that should be the case for other plugin-handling routines as well?

  • References:
    • [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
      • From: didier
    • Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
      • From: Luis EG Ontanon
    • Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
      • From: Guy Harris
  • Prev by Date: Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
  • Next by Date: Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
  • Previous by thread: Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
  • Next by thread: Re: [Wireshark-dev] [PATCH] wireshark doesn't compile if configure --with-plugins=no
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation