ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Ethereal-dev: Re: [Ethereal-dev] Installing Plugins (0.10.14)

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

From: "Guy Harris" <gharris@xxxxxxxxx>
Date: Fri, 27 Jan 2006 17:28:14 -0800 (PST)
Gilbert Ramirez wrote:
> I'm not sure what you mean by "using a single setup file for windows".
> But, the NSIS installer puts the plugins in the correct location, but
> the build environment does not do that.

...and isn't supposed to do that; it's building, not installing.

"make install" on UN*X (and Cygwin?) builds installs the plugins, as does,
as you note, the NSIS installer.

Running from the build directory is mainly done, I suspect, by people
testing a build.  Perhaps some mechanism to allow Tethereal and Ethereal
to determine that they're being run from a build directory (one could use
an environment variable on UN*X, although that'd be more of a pain on
Windows), and to have them

    determine what directory that is (easy on Windows - in fact, we
already *do* determine that - but trickier on UN*X; it might involve
looking at argv[0] and:

        if it has no / in it, searching $PATH for the appropriate binary;

        if it has a / in it, but doesn't begin with a slash, combine it
with the result of getcwd();

        if it has a / at the beginning, use it);

    use that directory as the "data directory";

    look for plugins not in a "plugins/{release number}" directory, but
scan all directories under "plugins" for plugins;

if they're being run from a build directory.