Wireshark-commits: [Wireshark-commits] rev 20261: /trunk/ /trunk/doc/: Makefile.am /trunk/epan/: epan.c epan.h filesystem.c filesystem.h libwireshark.def plugins.c plugins.h proto.c proto.h /trunk/gtk/: about_dlg.c main.c /trunk/: dftest.c tshark.c

From: guy@xxxxxxxxxxxxx
Date: Tue, 02 Jan 2007 06:49:42 GMT

http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=20261

User: guy
Date: 2007/01/02 06:49 AM

Log:
 Add a WIRESHARK_RUN_FROM_BUILD_DIRECTORY environment variable on UN*X;
 if set, and if the program isn't running with additional privileges,
 it'll treat the directory in which the program is found as the data
 directory.
 
 If, on Windows, the version-number subdirectory of {data
 directory}\plugins doesn't exist (which is assumed to mean that the
 program is being run from the build directory), or if, on UN*X,
 WIRESHARK_RUN_FROM_BUILD_DIRECTORY is set, the plugin directory is the
 "plugins" subdirectory of the data directory, and all subdirectories of
 that directory are scanned for plugins, as the "plugins" subdirectory of
 the build directory contains subdirectories for the plugins; this means
 that if we're running from the build directory, we'll find the plugins
 we built in the build tree.
 
 When generating the wireshark-filter man page, run tshark with
 WIRESHARK_RUN_FROM_BUILD_DIRECTORY set, so it uses the plugins from the
 build to generate the list of filters.

Directory: /trunk/doc/
  Changes    Path           Action
  +1 -1      Makefile.am    Modified

Directory: /trunk/epan/
  Changes    Path                Action
  +2 -23     epan.c              Modified
  +1 -1      epan.h              Modified
  +134 -5    filesystem.c        Modified
  +17 -0     filesystem.h        Modified
  +3 -1      libwireshark.def    Modified
  +58 -68    plugins.c           Modified
  +1 -5      plugins.h           Modified
  +9 -14     proto.c             Modified
  +2 -4      proto.h             Modified


(4 files not shown)