This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Output uv4 build messages to stdout

I'm building my project via the command line using something like this:

"C:\Program Files\Keil\UV4\Uv4.exe" -b ".\myProj.uvproj"

The problem is that this command does not send anything to the stdout. The only option I see is to output the results to a file, using the -o option. Is there any way of just showing the results in the same command prompt window without resorting to some ugly hack?

Also, is there any way to perform a clean on a project via the command line?

Parents
  • Per,

    I really appreciate your statements in the final posting on the thread regarding tool
    installation locations.

    http://www.keil.com/forum/16556/

    Keil really does appear to think only in terms of small-code projects, with a single developer. They do not appear to consider the Production Software use model, where multiple developers commit their source to a shared repository and an autonomous machine automatically performs the "definitive" build.

    For the cost of the tools, I'm a bit underwhelmed, particularly considering the quality of their support.

Reply
  • Per,

    I really appreciate your statements in the final posting on the thread regarding tool
    installation locations.

    http://www.keil.com/forum/16556/

    Keil really does appear to think only in terms of small-code projects, with a single developer. They do not appear to consider the Production Software use model, where multiple developers commit their source to a shared repository and an autonomous machine automatically performs the "definitive" build.

    For the cost of the tools, I'm a bit underwhelmed, particularly considering the quality of their support.

Children
  • I think the list of users who would want Keil uVision a bit better adapted to automatic builds, version control etc could be made very, very long.

    Alas, we don't have the ear of the responsible developers/managers, or they simply have a completely different view on software development and work processes in different companies.

    I'm not sure how often they travel around and meets their customers at the customers place (instead of quick meets at fairs or meeting new customers when they hold seminars/courses), but I do suspect that they have not really spent some real time looking at real-life needs.

    They are more interested in how to make sure each company pays multiple licenses of not only the uVision system but all the source code bundles too than they are in thinking about build machines, version control, regression testing etc.

  • Agree. We're a huge customer for ARM (mostly processor IP) but don't seem to have their ear. It's worse with Keil, which still seems like a separate company. I like their stuff, definitely prefer it to IAR, but its idiosyncracies are getting more amd more out of touch with the main stream. At this point Hitex seems a lot more responsive to our requests, we'll see where it goes...