How do I use system environment variables to specify a path to a source file?
"The uVision is probably fine for the 'typical' case, but beyond that it is worthless." Example of something beyond the "typical" case: The Triscend E5 contains an 8032 and some programmable logic integrated onto a single chip. Therefore a "build" for an E5 consists not only of the "normal" application firmware - as for any 8032 - but also the programmable logic configuration, and then combining the two into a single PROM image. By using the uVision facilities Jon mentioned, I have made uVision Projects which can include the entire process (both "software" and "hardware") into a single uVision "Build". The major stumbling block, as I mentioned earlier, is the lack of any dependency checking with Custom Translators. :-( While not entirely "worthless" this does severely limit the usefulness of this facility. :-( Just being able to click the Group or item and choose 'Run Custom Translator Now' would be a major help! Therefore I don't usually bother these days; I use the separate Triscend tools for the programmable logic "build", and just do the final combining & download in uVision - as I described in Application Note 159: http://www.keil.com/appnotes/files/apnt_159.pdf