don't jump to '<source>.o' upon linker error

Completed

Follow

frank meyer

• May 20, 2012 17:09

This is less a suggested feature, but something I find a little annoying.

Upon a linker error, the CrossStudio GUI is opening the 'offending' file, which is usually an object file in this case. While this makes sense for preprocessor or compiler errors, there is no information gained in this case. I just see a window named "<sourcefile>.o", and in this window the string "ELF" in the midst of unprintable characters, and a blank screen otherwise. It can become annoying to close this window after each error...

I did not find any possibility to turn this feature off, though...

0

• 

  Jon Elliott

  • May 21, 2012 11:28

  This is a bug in the current version of CrossWorks for ARM (2.2.0), it will be fixed next release.

  0

  Comment actions Permalink
• 

  Rob

  • June 07, 2012 11:04

  I too have been wondering why it keeps opening the object file of the offending module, upon linker error. Look forward to seeing a fix

  0

  Comment actions Permalink

Please sign in to leave a comment.