I am evaluating uVision3. I have problems when trying to use GNU toolchain. I first created a new folder which includes the defautl startup.s file. I copied and pasted the pot.c file from C:ADuC_Beta702x\Code\...ADC\pot.c. I have already installed the GNU(GCCARM331.EXE from CD). When I hit the "translate" icon, I get: compiling pot.c... arm-uclibc-gcc: cannot specify -o with -c or -S and multiple compilations pot.c - 0 Error(s), 0 Warning(s). I can not do build or do anything from here. Can anyone help? Thank you
hey guys...it was quite simple. KEIL apparently hates long file names. i initially installed KEIL into C:\Program Files\KEIL...which was the problem. i reinstalled to C:\KEIL which works fine now. yes there were no errors, but i still couldnt build anything. i rebuilt all the files and it wouldnt create the target. i'd get the following after i tried to build: Build target 'Target 1' compiling pot.c... arm-uclibc-gcc: cannot specify -o with -c or -S and multiple compilations assembling startup.s... Assembler messages: Error: Error: can't open Files\KEIL\ARM\INC\ADI\ for reading Files\KEIL\ARM\INC\ADI\: No error Target not created thanks for the help though!
"KEIL apparently hates long file names. i initially installed KEIL into C:\Program Files\KEIL...which was the problem" Actually, I doubt that it has anything to do with Keil. It's probably not even long filenames, but the use of spaces in file and/or folder names! Remember, GNU is of UNIX origin; UNIX doesn't mind long filenames, but doesn't do spaces in filenames!
Remember, GNU is of UNIX origin; UNIX doesn't mind long filenames, but doesn't do spaces in filenames! GNU tools, like most Unix tools of these days, can deal with spaces in filenames quite fine --- if you pass them in correctly, so blanks inside arguments can be distinguished from blanks separating arguments. The onus is on uVision, here: it should have either quoted this -I argument, or generated a message at installation time that blanks in filenames had better be avoided. This is not a Unix particularity at all, but rather a general feature of all command-line tools facing blanks in filenames. The problem is actually a lot more common on Windows than on Unix. Unix people usually know enough about command line usage to avoid putting blanks in the middle of a filename. Microsoft, OTOH, decided to force this misery on everybody, by using as many long filenames with as many spaces in them, in a default installation, as they could get away with. Thus "Program Files" instead of "Programs", and "Documents and Settings" instead of "Home" or "Users"
"Microsoft, OTOH, decided to force this misery on everybody, by using as many long filenames with as many spaces in them, in a default installation, as they could get away with. Thus 'Program Files'..." Absolutely - complete idiocy!
View all questions in Keil forum