Ethereal-dev: Re: [Ethereal-dev] Decoding of tektronix K15 files not performed ; frame showed

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 <gharris@xxxxxxxxx>
Date: Thu, 04 Aug 2005 10:21:27 -0700
LEGO wrote:

I was thinking in either using a #defined name (making trunks's
configure script pass it to wiretap's config script) or may be better
adding a function to wiretap to set the config directories and having
it called by [t]?ethereal very soon at initialization.
The former being more feasable (every time I have to deal with
configure scripts I get a headache).
The former (which involves monkeying with configure scripts), or the latter (which doesn't), being more feasible?
The latter lets the user specify different configuration files, if necessary, for different input files, without having to reconfigure and rebuild Ethereal.
It also might, if done sufficiently generally, be useful elsewhere (e.g., it could be used to handle capture files where the software *can't* automatically figure out the right thing to do, e.g. for libpcap an option would let the user say, at open time, "this file is one of those annoying Nokia IPSO captures", rather than having to run it through that "denokify" program I wrote).