Ethereal-cvs: [Ethereal-cvs] cvs commit: ethereal/epan config.h.win32 filesystem.c filesystem.

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <guy@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 21 Aug 2001 01:39:18 -0500 (CDT)
guy         2001/08/21 01:39:18 CDT

  Modified files:
    epan                 config.h.win32 filesystem.c filesystem.h 
                         plugins.c resolv.c resolv.h 
  Log:
  On Windows, use the directory in which the binary resides as the
  directory in which global data files are stored.  If an installed binary
  is being run, that's the correct directory for them; if a build-tree
  binary is being run, the "manuf" file will be there, and you can put
  other data files there as well, if necessary.
  
  Do the same with plugins, except that, if there's no
  "plugins\\{version}" subdirectory of that directory, fall back on the
  default installation directory, so you at least have a place where you
  can put plugins for use by build-tree binaries.  (Should we, instead,
  have the Windows build procedure create a subdirectory of the "plugins"
  source directory, with the plugin version number as its name, and copy
  the plugins there, so you'd use the build-tree plugin binaries?)
  
  Move "test_for_directory()" out of "util.c" and into
  "epan/filesystem.c", with the other file system access portability
  wrappers and convenience routines.  Fix "util.h" not to declare it - or
  other routines moved to "epan/filesystem.c" a while ago.
  
  Revision  Changes    Path
  1.8       +1 -3      ethereal/epan/config.h.win32
  1.5       +137 -3    ethereal/epan/filesystem.c
  1.4       +21 -3     ethereal/epan/filesystem.h
  1.28      +36 -72    ethereal/epan/plugins.c
  1.12      +18 -4     ethereal/epan/resolv.c
  1.7       +1 -2      ethereal/epan/resolv.h