>> My only outstanding problem is that the build area into which >> all code, and now documentation, is built is separate from the >> source tree.
>Would ``Edit/Preferences/Paths/Use Temporary Directory'' help? >Matej Not really, unless there is a way of setting it from the command line at the time lyx is invoked to do the export, and I'm not sure this controls the location of the exported file anyhow. My requirement is that I am able to build all our documents as a batch process without any gui interaction at all and without any dependence on fixed paths since all the material for the documents goes into CVS along with our source code and could be checked out in a completely different location. It's the ability to do this which makes lyx/miktex attractive. It allows us to build and manage our docs just like we build and manage our source. I was really pleased to find a windows version of lyx (where most of our development is done) because at last there's some hope of managing documentation rationally instead of suffering with MSWord. We already use doxygen for most of the technical docs (APIs etc.) but user guides have still given us a problem. In the end I've just extended my perl scripts to copy the image files to the build directory. Its a bit crude, but it works fine. guy
