According to Sunny Fortune: > I've noticed something strange in the way the > configure program works. I'm not sure whether I'm > doing something wrong. > > I edited the CONFIG file to change the values so that > all paths are relative. For example, setting prefix to > be the current directory. And when I run the configure > program, the settings revert back to the original > values. > Are we allowed to edit the CONFIG file, or do we need > to set values via the flags from the command prompt. > And if so, how do we set values to read relative paths > only?
The ./configure script regenerates several files from their corresponding ".in" files. CONFIG is regenerated because some, but unfortunately not all of the paths in there can be specified as configure command line arguments. If you want to make permanent changes that are configure-proof, edit CONFIG.in instead, then run ./configure. I don't know that there's any way of using relative paths only and still have everything work correctly. I think several of the programs need fully qualified file and directory names because they're not guaranteed to be run from the same directory all the time. Perhaps I'm wrong, though. At the very least, htsearch is not likely to run from the same directory as htdig and htmerge. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ 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
