I have one project to compile, but encounter the following messages.
Is it due to the versions or any hardware requirements? because I have been
used other computer to compile, it's ok to run.
*** Using Compiler 'V5.06 update 1 (build 61)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin' Build target 'Target 1' compiling sys.c... compiling gpio.c... gpio.c(30): warning: #1-D: last line of file ends without a newline } compiling retarget.c... compiling system_Nano100Series.c... compiling gpio.c... linking... .\Objects\test.axf: error: L6002U: Could not open file .\objects\gpio.o: No such file or directory Finished: 0 information, 0 warning, 0 error and 1 fatal error messages. ".\Objects\test.axf" - 1 Error(s), 1 Warning(s). Target not created. Build Time Elapsed: 00:00:11
Interesting that the linker fails to open the specific object file that the compiler earlier produced a warning for. Just that a warning should not result in a compilation failure.
Might you have any setting "Treat warnings as errors" and the compiler then fails to realize that it should also upgrade the printout from a warning message to an error message?
I am not quite sure where I can set "Treat warnings as errors", Can you tell me how I can
solve this ?
So you didn't decide to try the simple route of just adding a single newline character? Thereby removing that single warning. If that solved the problem, then you would know that the compiler did treat the warning as an error.
If you then get the same linking error even without any compilation warning, then you would know that you need to look for a different reason - like possibly having the compiler actually produce an object file - but in a different directory than where the linker looks for it.
My computer seems to occur an unpredicted errors when compiling the .c files. I guess the
software might need an appopriate hardware requirements. I switch to another desktop pc for
testing, the compling problems has disappeared and work function good !!!
I don't think so that the software can not find the .object files , it mainly caused by
executing the c codes, which producing the unpredictable errors . !!!