Ethereal-dev: [Ethereal-dev] Re: Plugins and ETHEREAL_STATIC

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

From: Ruud Linders <moztest@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 08 Aug 2003 16:29:37 +0200


As nobody replied to me questions about building plugins as static,
can I conclude nobody knows/cares/uses these "static' objects ?

To original idea seems to have been to make it possible to include
the decoders in the plugin directory directly into the main 'ethereal'
binary as opposed to the seperate plugin object.

Currently this doesn't work and it is debatable if it should be made
to work. My proposal would be to rip this stuff out.

I would be happy to generate a patch, let me know.

Regards,
	Ruud Linders


There is something about the building of plugins that I don't get.

This is what I usually configure :

./configure --enable-static=no --prefix=/usr

(according to configure --help this enable=static=no is default anyways)
Then simply 'make' and a quick cop of coffee later everything is built.



However, when I do 'make' again (or 'make install') always the static
part of all the plugins is compiled again (see attached part of make output).
Obviously this is rather annoying.


But why are we building these 'static' objects anyway ?
- using ./configure --enable-static=yes doesn't seem to include the plugins
  into the main ethereal binary anyway
- do the licenses allow building plugins into the main binary ?