How can I use GNU compiler in Keil uVision3 evaluation version?

If you want really good results, you should move to the newest GNU releases.

E.g. this is also written on the page that I point you to:
>Code generation for Thumb mode has reportedly been >improved in GNU GCC 3.4.3...

Current version is arround 4.2. Not only compiler is improved but also libraries were optimized (and this can have a big influence to the generated code).

What is a problem is the setting of uVision environment for the newest GNU tools as you can see from many threads in the Keil forum. The settings is not as easy as for officialy supported GNU version downloaded form Keil webpages.

If you want really good results, you should move to the newest GNU releases.

E.g. this is also written on the page that I point you to:
>Code generation for Thumb mode has reportedly been >improved in GNU GCC 3.4.3...

Current version is arround 4.2. Not only compiler is improved but also libraries were optimized (and this can have a big influence to the generated code).

What is a problem is the setting of uVision environment for the newest GNU tools as you can see from many threads in the Keil forum. The settings is not as easy as for officialy supported GNU version downloaded form Keil webpages.

"officialy supported GNU version downloaded form Keil webpages."

I think you'll find that GCC is not actually supported by Keil at all - it's purely on a "as-is" basis.

As is generally the case with free software, of course!

Andy, you are definitely right.

Actually I wanted to say, that GNU version downloaded from Keil
webpage works correctly with uVision.
This is not the case with newer versions.

Sorry for confusing formulation.

"Remember: Cygnus is basically unix for windows - and unix doesn't support spaces in filenames"

Unix doesn't have any problems with spaces. It just has a different way of handling them than broken Windoze. If the path is encapsulated in quotes or the space is prefixed by a break character, they will be processed ok.

This requirement is needed to make sure that a path is always processed the same way, insted of the OS trying to auditected if the space is a separator or part of a name.

I stand corrected.

"If the path is encapsulated in quotes they will be processed ok."

That should also apply to the windoze command line.

However, in the past, uVision-2 had problems with correctly doing the encapsulation.

I don't know if those problems were ever fixed in uVision-2, nor if uVision-3 has inherited them - I just play it safe and never use spaces in path and/or filenames where the Keil tools are concerned.

Many other toolsets have similar problems (including those that use Cygwin) so my general principle is never use spaces in path and/or filenames.
At least that way you know that you're safe!

See this Microsoft article for how to change the 'My Documents' folder name - eg, to something without that stupid space:
support.microsoft.com/.../en-us

I have successfully done this on 2 systems now.

But is there a way to similarly rename 'Program Files'...?

See: www.8052.com/.../read.phtml

Hmm. "auditected" must be the most interesting spelling error I have managed in a while. Sounds like it has something to do with audio...

I really can't see how I could have managed to convert "autodetected" to "auditected" :)

A problem here is that some programs do follow the M$ guilelines how to access "My Documents" and some just hard-code "C:\My Documents\".

Since a Win system that has been up for a couple of years and having a lot of programs installed tends to be a bit fragile, it is extra hard to know if that fragility is caused by the system or by individual applications being buggy and making assumptions that they are not allowed to make.

And I didn't even notice it!

Have you been borrowing Erik's kyeborad...?!

;-)

Yes, it is probably contagious :)