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.
I read an earlier entry that asked how to integrate CodeWright with the Keil compiler. The answer was that a third party company provides an IDE that does it. I would like to configure CodeWright to build using the Keil tools rather than to buy more tools that replace the ones I already own. I prefer not to have to use makefiles or batchfiles. Keil's integrated make utility is very nice and it seems that there should be a way of utilizing it from Codewright but I have no idea how. Does anyone have any insight on if and how this can be done? Thanks in advance, any help is much appreciated.
Sorry, I should have mentioned that I did read though that chapter and spent about a day trying to get things working without success. If I spent a couple more days stuggling through it I would like to think I could get things figured out and if there is no earier way I will probably end up doing just that. I just what I'm wondering is, is there such a thing as template files or add-ins out there somewhere that will configure Codewright for various compilers including Keil? If not I sure wish there were.
I have makefile that I call from CW32 v6.5. I make sure to set the working directory explicitly as sometimes it appears to do nothing when set to %x. There are Keil error parses builtin or available to make the build output clickable for easy error location. Works like charm. - Mark
I was really hoping to get away from makefiles but it might be worth it to save switching back and forth between applications. Thanks Andrew and Mark for your help.
For compiles, you can simply enter c51 %r%e oe sm noip in the comple line and be happy. I call the makefile to build the code since it is somewhat difficult to teach CodeWright to compile only changed files and then link. I also like to check Redirect Output, No Command Shell, Save All Files, Background, and Use VDOS. - Mark
I was really hoping to get away from makefiles At least with a makefile you can escape Keil's insistence on rebuilding all files with the SRC directive, whether they need it or not ;-) Anyhow, it is possible to run uVision from a command line, have it build a project, save the results in a logfile, and exit; eg,
uv2.exe -b -o logfile project
Thanks Mark: That information is definately helpful. Is it just me but doesn't this seem like it should alot simpler. I just want the build button in CodeWright to launch uVision2, load a project and trigger Keil's build process using its integrated make utility. Basic menu commands that already exist in uVision2. If this can be done, the mechanisms are already in place to allow CodeWright to do the error parsing half of the job. Walt
Thanks Andrew: I think you may have answered the question I asked in my last reply before I had the chance to ask it. Now that's service ;-) Thanks again to all for your timely responses and help in this matter. It looks like I have several possible solutions to try. Walt
Oh ho! You want to invoke uVision! That I did not understand. If uVision had some DDE interface it would be cool. However, if you can find any command line documentation for invoking uVision you may be able to do something with it. However since you'd need to keep calling it over and over again, I don't think this would work well since you'd have to kill the last invocation each time. - Mark
Andrew: I tried your suggestion and it works exactly how I was hoping. Thanks to you and Mark for sticking with me and helping me thru this. Walt
If uVision had some DDE interface it would be cool uVision does have some DDE interface, but cool it is not :-( It allows you to issue the same debugger commands that you can issue on the debug command line, but it's only debugger commands, and there's no way to retrieve the results of the commands! See App Note 143 (and I posted some questions here about a year ago)