Dmitry Hayes wrote:
You are correct, there are more then one way to specify include/lib/executable setting ...
Off the main topic of this thread, but I strongly urge you to dispense with the idea of changing the global paths in VC++. This is a pain for those of us who cannot have xerces in our include and lib paths for other projects. A global environment variable such as $INCLUDE suffers from similar problems.
A better solution, in my opinion, is to use a specific environment variable (eg, XERCESINCLUDEPATH) and use that variable name in the the project (dsp) file. This only requires that users add a couple of environment variables, which is no more difficult than changing the VC global directories, but is less invasive. Also, you can then use the same approach in windows and *nix builds.
Don
