When I try compile my software, I have the following error :
arm-none-eabi-gcc: error: ..srckernelmutex.c: No such file or directory
There is no backslash in the path, normally is ..\src\kernel\mutex.c
why ? anyone can help me ?
Have you considered using / instead of \ as path separator, since C uses \ as break character in strings?
Under uvision, I created a target and a group, put in the file mutex.c In "components, environement, books" I select GCC I try to compile and get this error : arm-none-eabi-gcc: error: ..srckernelmutex.c: No such file or directory
So have you checked that a file named srckernelmutex.c does actually exist anywhere on (or accessible to) your machine?
If the file does exist - is it in a place where you have configured the tools to find it?
Hi Andrew,
My file is called mutex.c and it is in directory ..\src\kernel. gcc return an error srckernelmutex.c not found, it is like uvision remove separator slashes or backslashes (I don't know, I'm new in windows world)
gcc return an error srckernelmutex.c not found, it is like uvision remove separator slashes or backslashes (I don't know, I'm new in windows world)
Close, but not quite. The problem is that your GCC (or possibly a Unix-style shell sitting between it and uVision) expects a Unix-like command line (with forward slashes as the directory separator), while uVision passes it a MS-style one (with backslashes filling that role). Backslashes mean a totally different thing to this GCC than uVision tried to use them for. They're for esacape sequences, e.g. for embedding special characters or blanks in file names.
In short: this GCC doesn't behave like a Windows program, but uVision expect it to. This combination cannot work.
Thanks Hans,
I change my GCC tools chain to code sourcery tools chain and I always have the same issue. I don't know why, keil says uvision is compatible with code sourcery tools chain and I have followed keil's installation guide.
You haven't still told us exactly where the tools pick up that path to your file. If it is the project file or part of a path somewhere in a setting or if you even play with #include.
View all questions in Keil forum