Tool/software:
Hi,
So a few months ago, i upgraded to CCS 20, only to find problems with source files that had 8859-1 encoded text strings. Then it was suggested to enable autoGuessEncoding, and add some comment early in the file that included some typical characters of this encoding.
That worked but I had warnings compiling "invalid character encoding". Output was ok though.
So now I had to add more strings to the same file, and the problem came back. Searching the net, it looks like this autoguess is full of problem.
In the old eclipse, one could just enter the file encoding manually on a file, but this setting is not available in CCS.
Is there a proper fix for this now? I tried to update to 20.1.1, but still it does not work.
I can live without editing this file in CCS, and instead use a proper file editor like Geany. But when I built the project outside CCS (gmake, in Release folder), and then start the CCS debugger, it rebuilds and the character set is again not working in my target. Or at least this is my guess. I don't understand how the debug/build process works in CCS, why it rebuilds, or if this is the problem, or if the compiler is the problem.
Target is cc2340, and the compiler seems to be ti-cgt-armllvm_4.0.2.LTS tiarmclang.
I need a way to work around this, and are stuck now.
