We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
How do I use system environment variables to specify a path to a source file?
Right, I just didn't see that right away, but have already done that. Thanks
My build is a bit beyond the questions asked here so it is dead easy to do whatever you want using a .bat file. The uVision is probably fine for the 'typical' case, but beyond that it is worthless. For uVision to be able to handle 'industrial stength builds', it will need to add ther possibility of running .bat files at strategis places. Erik
For uVision to be able to handle 'industrial stength builds', it will need to add ther possibility of running .bat files at strategis places. uVision2 has the ability to run .BAT or any other program file anywhere in the project build process. All you have to do is add the program file to the project and move it where you want it to run. The only tricky part is that you must specify the program path and name in the arguments line on the custom translator dialog. Jon
"but beyond that it is worthless" I wouldn't go as far as "worthless," but uVision's Project management facilities certainly do have serious limitations - as I have mentioned on this forum several times before; eg * There is no way to specify options common to more than one Target; * It is not possible to re-order the Groups within a Project. This one is unforgivable, as the order of things within a Project defines the order in which they're done! * There is no way to specify dependencies for Custom Translators - it's just "Always Build" or "Never Build". It would be useful if there was at least the option to right-click a file or Group and choose to rebuild (translate) that item - currently, if you've unchecked 'Include in Build' you can't even "manually" trigger a rebuild of the item :-(
"but beyond that it is worthless" I wouldn't go as far as "worthless" well, the key phrase is "beyond that". I am bulding 7 different executables based on mainly the same source and that is "beyond that" Erik
"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