I guess what I'm asking it, if you don't pass the config attribute to htsearch, how does it know the location of the default config file? If the answer is still "it's specified in CONFIG", then the
The config attribute only specifies the base name of the config file; it doesn't really have anything to do with actual location.
next question is, is there any way to retrieve what htsearch thinks is the location of the default conf file _after_ compiling?
I don't think there is a way to actually query htsearch directly, but if you run the 'strings' command against htsearch, you can probably pick out the path. I would start with something like the following.
strings htsearch | grep conf
The bottom line is, I'm trying to put together an "admin" utility for managing conf files, but the first step is asking htsearch where it thinks conf files are located (in cases where users pick non-standard locations).
If there is a way to do this directly, I am not aware of it. If you have control over the installs, you might want to tweak things such that a file containing the path is created as part of the install.
Jim
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
