Tool/software: Code Composer Studio
Hello,
I was redirected to the CCS Forum after I asked this question:
The problem was solved - but if the cause was what Ralph explained - I don't understand why it happened only with UARTprint...
Please help.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
Hello,
I was redirected to the CCS Forum after I asked this question:
The problem was solved - but if the cause was what Ralph explained - I don't understand why it happened only with UARTprint...
Please help.
shai kon said:So if uartstdio.c was to be added (for the purpose of argument) to "Debug" , "targetConfigs" , "Binaries" , etc there wouldn't be a problem ?
"Debug" is a special generated folder for build output. Do not put any source files in there. Source files in there will also be skipped. It will be picked up in "targetConfigs". "Binaries", like "Includes" is a "pseudo" node and it is not possible to add any source files to it.
shai kon said:If my understanding is correct - can you please explain the motivation behind this ?
"Includes" is simply a graphical representation of the include search paths added to the project properties. Similar to how "Binaries" is a graphical representation of the executable generated from the project build. It is a quick way for users to see what include search paths are specified in the project properties and if any generated executables are present. It is why they have different icons than the typical "folder" icon. This is something we inherit from stock Eclipse.