I built a project using STMCubeMX from ST, and it built. I added a few source files, added a couple of include paths, both using the GUI. It still tried to build, but the include paths were not correct, so I rearranged the order using the GUI.
Now I get: "Error: C4065E: type of input file '../Inc' unknown"
Is there manual "tuning" I can do to the uvprojx file? Do I now have to regenerate the project?
Any recourse? Bueller?
When playing with directory depths, and reconfiguring, I regularly pull the project files up in a text editor. Save a backup.
Any hints on what to look for? I compare to a "known working model" and the <IncludPath> sections differ by little or nothing. Sometimes there's a space between entries ("..\Somepath; ..\SomeOtherPath" v. "..Somepath;..\SomeOtherPath"), or the path separator changes from '\' to '/', but nothing clearly incorrect.
Thanks
Show the exact section of source code that's getting the error, and the exact, complete, unabridged message.
Use copy & paste - don't manually re-type.
Note the instructions for posting source code.
Thanks, Andrew. If there were any code involved, I'd do that.
I'm referring to a problem with the GUI, in which I have rearranged the order of the include file paths, and the include path description in the XML is no longer accepted by the translation tools. There's so very little information in the error messages that I cannot determine which piece of the toolchain is unhappy.
I apologize if I didn't make it clear that it's a GUI problem in my initial post.
which I have rearranged the order of the include file paths,
If such rearrangement has any effect at all, you shouldn't do it anyway, because that's dabbling with the symptoms, not curing the actual problem.
That's because the only situation in which the order of include path specification can have any effect is if there are multiple include files in the path which have the same name. That's just going to keep failing in terribly interesting ways, no matter how cleverly you rearrange your include path. So don't let that happen. Make your files' names unique instead.
... that I cannot determine which piece of the toolchain is unhappy"
So post the complete build output - maybe someone can spot something.
Error: C4065E: type of input file '../Inc' unknown
eg, the 'C' prefix to the code suggests that it's a Compiler error
Have you tried googling that error code?
Do you have spaces in your file or folder names?
Thank you. I never knew the toolchain errors were coded like that - guess that's what I get for going to University before compilers were invented. I have Googled the error message, which leads me back to asking in this forum. Oddly enough, the web search turned up very little information - plenty of questions, even specifically like this, but no answers, just like now.
In any event, I've moved forward. I have a project that builds, and I am unable to dedicate any more time to reproducing this error.
Thanks for your assistance.
You must be living in a very strange country, where they did have universities in the 1950s, but still haven't discovered the concept of retirement 60 years later...
Oddly enough, the web search turned up very little information
I'm calling BS on that. The very first google hit on the error number explains exactly what's wrong.
So does the error message text itself, if one spends a bit of time actually trying to understand it. It tells you that the compiler believed that something named "../Inc" had been given to it as an "input file", i.e. source code. Well, unless you have very weird file naming conventions in aforementioned country, "../Inc" is bound to be not the name of a file, but rather that of a directory, right? That means some part of your include path got split off from the rest, so it now looks like a separate command line argument, and that would normally be the source file.
So look at the actual set of compiler flags (uVision shows that right there in the GUI, too), and see where that isolated "../Inc" might be.
I have reproduced this problem. I had a project for STM32 from Keil. I didn’t touch it for 2 months. After 2 months, I needed to add a GPIO pin. I did it via STM32QubeMX. And I got the first bug. My * .h files from my directory were not connected to the main.c file. I got into the settings and saw that the directory disappeared from the settings. Added it. And the Error C4065E error popped up. I could not understand and went to search through Google. Saw this forum with an unreproducible issue. I decided to get to the bottom of it. Found that my directory with h files from "include paths" moved to "Misc Controls". By removing the false duplicate from "Misc Controls" everything compiled fine.
I am writing via Google Translate. Sorry if something is wrong.
I have reproduced this issue. Keil software for STM32. 2 months did not touch the project. I needed to add a GPIO pin. Added via STM32QubeMX. The project did not compile. Lost the directory with my * .h files. I added it to "Include Paths". But the project still didn't compile. This bug C4065E has appeared. I didn't understand what happened and started looking for an answer via google. Found this forum. I saw that the problem was one-time and is not reproducible. I began to look closely at the project settings and saw that the path to my * .h files is in "Misc Controls". Removed from "Misc Controls". Problem C4065E disappeared and the project compiled.
I am writing via google translate. Sorry if, what is wrong.