Don, I think we would like to avoid having the install directory 'baked in' to the nsd in any way (it enables builds to occur on different machines/locations and the install directory be moved around as needed without requiring rebuilds). For files that are not located via the normal $path, $LD_LIBRARY_PATH mechanisms, the nsd will first look to explicitly named configuration paths and values. For those items that are not specified, or which have a relative pathname, it needs to default to something. As it has no knowledge of where the install directory is, it makes usual assumption of basing locations relative to the current working directory (but assuming that 'bin'-type items will be in a 'bin' subdirectory) (the fact that your current working directory happened to be your source directory added some confusion)
In our runtime directories we usually have softlink to the install bin directory. e.g., <directory_we_run_from>/bin -> <install_dir>/bin Does this adequately address your concern? -Elizabeth Thomas America Online, Inc. [EMAIL PROTECTED] wrote:
When I do: make; make install; make distclean I end up with init.tcl installed in /usr/local/aolserver/bin, as I'd expect. Unexpected was the fact that AOLserver 4.0 won't start because distclean removed it and the bin directory from my local aolserver home. It's doing a Ns_HomePath (or whatever, my laptop's turned off at the moment) for directory "bin" and "init.tcl" Is this intentional? If it's installed in the install's bin directory I'd naively expect it to be looked for there just like other bin contents ... -- Don Baccus Portland, OR http://donb.photo.net, http://birdnotes.net, http://openacs.org
I. To remove yourself from this list: Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
