On Thu, 12 Sep 2002, Brian White wrote: > the "Yes" and "No" responses as expected ) but I have > no idea how to propogate my AC_DEFINE down to the > C++ code.
Run "autoheader" and it will update the include/htconfig.h.in , which becomes htconfig.h which is #included in the code. You should get your DEFINE set, and then you can #ifdef, #ifndef, etc. > Are there any problems with doing this? Are there > any conventions I should be following that I am not? Personally, if I don't have a system-level file-locking system, I'd implement one in user code, say with a .lock file in the same directory (if writable) or using TMPDIR and something like $TMPDIR/path-to-file.lock for locking /path/to/file. I've actually felt this might not be a bad addition to the htdig code anyway, since the databases really should be locked against multi-write until they have granularity. Does that make any sense? -Geoff ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
